1# !!!! PLEASE READ THIS BEFORE DOWNLOADING ANY FILES 2 3There have been a number of misunderstandings about the DPS8 GIT source 4code tree; sometimes leading to unfortunate user frustration. 5 6The canonical usage of GIT generally has the master branch containing 7“releases”; they are expected to be “ready to go”. Development takes place 8on branches; once the development branch is done, it is moved to the master 9branch as a release. The DPS8 emulator project is not following that model. 10 11With just a handful of developers, and any “release” being a hoped-for dream 12in the unimaginable future, the master branch is the bleeding-edge development 13code. Commit points on the master branch probably compile on the machine of 14the person making the commit, but there is no promise of functionality, 15portability correctness, update procedures, testing or even that it will 16compile. 17 18The Alpha 1.0 release was done as a tag on the master branch; this was poor 19planning on our part, as it made it difficult to apply bug fixes to generate 20a 1.1 version. The Alpha 2.0 release is being done as a branch; this will 21allow bug fixes to be merged in from the master branch, enabling the creation 22of release candidates, and future 2.x releases. 23 24As with the master branch, please realize that there is no guarantee or 25implied understanding that release candidates are to work or able to perform 26any useful function. In this way you, our user community, will not be under 27any false assumptions about the quality of our release candidate 28distributions. 29 30The DPS8M team would like to apologize for any difficulties our unorthodox and 31informal policies may have incurred. 32