User Tools

Site Tools


testing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
testing [2017/06/28 19:29]
be.ing
testing [2018/05/05 12:55]
be.ing [GitHub pull requests]
Line 9: Line 9:
 Our build server regularly makes new Mixxx installers from our master git branch [[http://​downloads.mixxx.org/​builds/​master/​release/​|available for download]]. We try to keep the master branch reasonably stable and not merge new features until we're fairly confident they are not going to create serious issues. However, if you want to perform with these, do so at your own risk. If you do decide to perform with a master build, test the same build for several practice sets before your gig to check that it works with your particular setup. If you encounter a bug, please [[reporting bugs|report it]]. Our build server regularly makes new Mixxx installers from our master git branch [[http://​downloads.mixxx.org/​builds/​master/​release/​|available for download]]. We try to keep the master branch reasonably stable and not merge new features until we're fairly confident they are not going to create serious issues. However, if you want to perform with these, do so at your own risk. If you do decide to perform with a master build, test the same build for several practice sets before your gig to check that it works with your particular setup. If you encounter a bug, please [[reporting bugs|report it]].
  
 +If you are using a GNU/Linux distribution other than Ubuntu or a derivative distribution that is compatible with Ubuntu .deb packages, you will need to [[compiling on Linux|compile from source code]] to test the master git branch.
 ===== GitHub pull requests ===== ===== GitHub pull requests =====
 If you would really like to be on the bleeding edge, you can try out [[https://​github.com/​mixxxdj/​mixxx/​pulls|pull requests on GitHub]] before they get merged to the master branch. This way you can be involved in the design of new features as they are being implemented. If there is an issue with a build from a pull request, comment on the pull request on GitHub instead of opening a bug on Launchpad. If you would really like to be on the bleeding edge, you can try out [[https://​github.com/​mixxxdj/​mixxx/​pulls|pull requests on GitHub]] before they get merged to the master branch. This way you can be involved in the design of new features as they are being implemented. If there is an issue with a build from a pull request, comment on the pull request on GitHub instead of opening a bug on Launchpad.
Line 14: Line 15:
 AppVeyor, our continuous integration system for Windows, builds each pull request and makes Windows installers. To get the Windows installer for a pull request, go to the bottom of the page on GitHub, click "Show all checks",​ then "​Details"​ for AppVeyor. On the AppVeyor website, click the 64 bit ("​dist64"​) or 32 bit ("​dist32"​) build, then click "​Artifacts"​ to get the link to the installer MSI file. AppVeyor, our continuous integration system for Windows, builds each pull request and makes Windows installers. To get the Windows installer for a pull request, go to the bottom of the page on GitHub, click "Show all checks",​ then "​Details"​ for AppVeyor. On the AppVeyor website, click the 64 bit ("​dist64"​) or 32 bit ("​dist32"​) build, then click "​Artifacts"​ to get the link to the installer MSI file.
  
-For Mac OS X and GNU/Linux, you will need to [[start#​compile Mixxx from source code]] yourself. ​You can set up the git repository ​on your computer to make it easy to [[https://​gist.github.com/​piscisaureus/​3342247|checkout ​pull requests ​locally]], then compile them.+For Mac OS X and GNU/Linux, you will need to [[start#​compile Mixxx from source code]] yourself. ​Refer to the [[Using Git]] wiki page for how to set up Git on your computer ​for downloading the code to test pull requests.
testing.txt ยท Last modified: 2018/05/05 12:55 by be.ing