OK, in this case I'll just go through the list of commits and find the corresponded issues which were fixed. I do not know what to do with tons of commits that were not included previously into the release branch. Maybe I'll save them as some kind of 'ChangeLog'.
Best regards, Vitalii Koshura 2017-03-29 17:00 GMT+03:00 Oliver Bock <oliver.b...@aei.mpg.de>: > 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.
