Soren Hansen wrote: > Putting release notes in the git repo so that they simply will get > merged along with the corresponding code seems like a no-brainer. What > am I missing?
For stable branches it prevents us from just backporting master changes using straight cherry-picks. For example you want to tweak the stable release notes for every CVE you end up fixing post-release in the stable branch. You have a master fix that happens to update the master release notes. Cherry-picking that will not cover your stable release notes, so you'll have to alter the fix to drop the master release note change and add a stable release note change. Doesn't mean it's not an option, but it adds pain compared to the current situation. -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
