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

2016-09-02 Thread Jeffrey Zhang
release note just generate a bunch of html file. We can not use them for track bug/issue. For example, how to trace the backport/revert/re-open status for some issue/feature if the reno notes is the only thing we have? The reno is just a releasenote tool. It is not helpful for project management.

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

2016-09-01 Thread Paul Bourke
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 wrote: Do people f

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

2016-08-31 Thread Steven Dake (stdake)
ons)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] Requirement for bug when reno is present On 30 August 2016 at 11:42, Paul Bourke mailto:paul.bou...@oracle.com>> wrote: Kolla, Do people feel we still want to require a bug-id in the commit messag

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

2016-08-30 Thread Christian Berendt
> On 30 Aug 2016, at 12:42, Paul Bourke 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

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

2016-08-30 Thread Steven Dake (stdake)
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, "P

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

2016-08-30 Thread Dave Walker
On 30 August 2016 at 11:42, Paul Bourke 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 a

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

2016-08-30 Thread Paul Bourke
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? -