sdake kindly took the time to explain the release process. Logs are
here:
http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2016-09-01.log.html#t2016-09-01T09:06:49
On 30/08/16 20:31, Christian Berendt wrote:
On 30 Aug 2016, at 12:42, Paul Bourke <paul.bou...@oracle.com> wrote:
Do people feel we still want to require a bug-id in the commit message for
features, when reno notes are present? My understanding is that till now we've
required people to add bugs for non trivial features in order to track them as
part of releases. Does/should reno supersede this?
I think it makes sense to keep the bug/blueprint id because some of our
features are distributed in several reviews and only one of the reviews
includes the release note. When removing the bug/blueprint ids from the commit
message when a reno note will be added with one of the reviews it will be
difficult to track the relations.
Christian.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
