@Oliver, I want to build a list of recommended commits to be integrated into release branch. The list of 'fresh' commits (after 6.6.33) will be very short (less than 100 commits). Also I want to see older commits which were not released for some reasons (maybe some of them were just missed) and give them a chance to be reviewed one more time.
Best regards, Vitalii Koshura 2017-03-29 11:27 GMT+03:00 Oliver Bock <[email protected]>: > On 29/03/2017 10:17 , Vitalii Koshura wrote: > > Merge commits are not good candidates to be merged integrated into > > release branch because it's hard to understand what commits were exactly > > merged. > > Ah, we seem to have a misunderstanding here. I thought you were > gathering a list commits such that a changelog for the latest client > release could be compiled. > > The above sounds like you want to create a release branch after David > released the latest client from some (still unknown?) commit. If this is > the case, do you really want to built that branch manually by > cherry-picking commits? > > Oliver > > > _______________________________________________ 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.
