Bugfix Workflow

Bugfix Work Flow

This is a brief step by step description about a typical work flow of fixing a first Mixxx bug. Follow the links for more details.

Fork Mixxx on GitHub

The Mixxx repo is located here

https://help.github.com/articles/fork-a-repo

Create a Local Branch

Mixxx workflow with GitHub

Using Git for Mixxx Development

Build Mixxx

Build Mixxx

Choose a working environment

You can edit Mixxx's code in anything from a basic text editor to a professional IDE (Integrated Development Environment.) We've had good experiences with Eclipse, but some of our developers just use text editors that handle multiple files and support syntax highlighting such as Kate or Notepad++. If you're working from a text terminal, GNU Nano also supports syntax highlighting, though it's not quite as thorough as many of the graphical ones.

Adopt an easy bug on Launchpad

List of bugs tagged as easy

More details you will find here: The Bug Tracker

Ask for hints and help

Ask your questions or discuss your ideas at

• mixxx-devel (mailing list)
• or at the Mixxx IRC Channel: #mixxx on Freenode.

Fix it!

Happy coding :-)

And don't forget to ask if you get stuck!

Issue a pull request

https://help.github.com/articles/using-pull-requests

Fix issues from codereview

This is the most annoying part. Because we are sometimes neat picker ;-)

Be sure that you code follows the Mixxx coding guidelines to avoid extra work.

Become a Mixxx Contributor

You have to sign a contributor agreement. We will contact you about it in time.

Fix is merged to Master

The Bug is fixed now and will be released with the next release cycle.

Your name will appear in the "About" box of Mixxx.