On 29/03/2017 15:24 , Jord van der Elst wrote: > 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.
Thanks for the reminder Jord. > 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. That's precisely my point. I'm talking about how it should be done to improve the situation :-) Branches and tags don't hurt don't even cost a thing. They just make everyone's (well, most people's) life much easier. > 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. There just two questions to answer: 1) Relative to which SHA1 do we need to compare (the start)? 2) Which commit was used to build the release (the end)? The is just a matter of running git log --reverse [more format-voodoo] start..end You can always shrink the result down (even automatically) if you want to exclude certain commits from the changelog. This way the changelog won't guesswork and require MUCH less work. Cheers, Oliver _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
