[openstack-dev] [kolla] Requirement for bug when reno is present

Christian Berendt berendt at betacloud-solutions.de
Tue Aug 30 19:31:11 UTC 2016

> On 30 Aug 2016, at 12:42, Paul Bourke <paul.bourke at 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160830/1d6fd671/attachment.pgp>

More information about the OpenStack-dev mailing list