The bug id and blueprint id are for automatic tracking via Launchpad. If they are omitted, managing the release becomes especially difficult. Unfortunately launchpad doesn't know about reno because then I'd agree, that would be an optimal way too go.
Regards -steve On 8/30/16, 3:42 AM, "Paul Bourke" <paul.bou...@oracle.com> wrote: >Kolla, > >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? > >-Paul > >__________________________________________________________________________ >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
