Skip to content

Bugfix Workflow

Daniel Schürmann edited this page Feb 12, 2014 · 49 revisions

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

Setup a powerful IDE

Pick your favorite IDE! We have made good experience with Eclipse

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

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.

Clone this wiki locally