On Wed, Mar 29, 2017 at 12:08 PM, Oliver Bock <[email protected]> wrote:
> > Given that BOINC currently uses master to integrate changes one should > branch off master when it's time to constitute a new release series, > like 7.7. Such a branch can then be used to build releases which will be > tagged individually (7.7.2). The branch will only receive bug fixes > afterwards, cherry-picked from master. > For clarity, BOINC has always adopted that the uneven release numbers were development versions, while even were release versions. Major.uneven.revision == development, Major.even.revision == release. In the past only when the development version had matured to stable enough would it branch off to a release versions, while all development happened in master. You can see this in github when checking the branches, the only branches available are the release branches (e.g. 6.6, 6.8, 6.10, 7.0, 7.2, 7.4, 7.6) While it would be nice to have a development version branched off to its own branch, with its own change log, this isn't how it was done in the past. I am still trying to figure out how to easily get the change log for 7.7.2 out for the public, because I am hampered by non-working Git GUIs on my Windows, so I'm now figuring out how to do this from the command line (thanks for that idea!). I suspect that the only person who knows the change log for 7.7.2 is David, and that he should at least make this one. Best, -- Jord van der Elst. _______________________________________________ boinc_dev mailing list [email protected] https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
