Since David has said that v7.7.2 was essentially a test build to verify that he
had all the build tools available for use, it might be best to regard that one
as a pre-alpha private build, and re-start the 7.7/7.8 development branch cycle
with proper version control from the outset.
On Wednesday, 29 March 2017, 15:00, Oliver Bock <oliver.b...@aei.mpg.de>
wrote:
On 29/03/2017 13:17 , Vitalii Koshura wrote:
> but currently we have another situation:
> master branch can not be a start point for new release branch.
It's not a matter of whether it should or even can be. It's a matter of
fact that the latest release (7.7.2) was build from master if I'm not
mistaken. Thus the release branch needs to reflect that, otherwise the
release and its branch would simply be inconsistent.
Best,
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.
_______________________________________________
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.
