Hello Oliver, Merge commits are not good candidates to be merged integrated into release branch because it's hard to understand what commits were exactly merged.
Thanks Best regards, Vitalii Koshura 2017-03-29 11:04 GMT+03:00 Oliver Bock <oliver.b...@aei.mpg.de>: > On 29/03/2017 9:40 , Vitalii Koshura wrote: > > From my POV the the most hard part of this is to select important > > commits only. > > As long as you ignore merge commits, which is easy given their common > commit message prefix, EVERY commit is important. Changelogs are for > *various* user groups and thus should be complete (you won't know what's > "important"!). Sure, this all depends on having proper commits (atomic, > message prefixes) in the first place, but that's a different problem. > > tl;dr: given our scarce resources changelogs should be created > automatically, as part of a proper release process. Proper commit > discipline is needed to facilitate that but it's easy to come by. > Disregarding commit discipline "in favor of" manual changelog harvesting > would be ridiculous. > > 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.
