Re: [openstack-dev] [release] process change for closing bugs when patches merge

Thomas Goirand wrote: > On 11/23/2015 10:58 PM, Doug Hellmann wrote: >> Right now, when a patch with Closes-Bug in the commit message merges, >> the bug status is updated to "Fix Committed" to indicate that the change >> is in git, but not a formal release, and we rely on the release tools to >>

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Excerpts from Thierry Carrez's message of 2015-11-25 10:19:44 +0100: > Thomas Goirand wrote: > > On 11/23/2015 10:58 PM, Doug Hellmann wrote: > >> Right now, when a patch with Closes-Bug in the commit message merges, > >> the bug status is updated to "Fix Committed" to indicate that the change >

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Hi Doug! Thanks for taking the time to gather opinions before going ahead. On 11/23/2015 10:58 PM, Doug Hellmann wrote: > As part of completing the release automation work and deprecating our > use of Launchpad for release content tracking, we also want make some > changes to the way patches

Re: [openstack-dev] [release] process change for closing bugs when patches merge

On 25 November 2015 at 05:26, Thierry Carrez wrote: ... > So it would be a shame to restrict task tracking possibilities to two > projects per bug just to preserve accurate change tracking in Launchpad, > while the plan is to focus Launchpad usage solely on task tracking :)

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Robert Collins wrote: > [...] > So, if folk do want bugs to sit in fix-committed, we can address the > timeouts really very easily: one (or two tops) projects per bug. We > should do that anyway because adding a comment to a bug is also able > to timeout, so our code is still going to suffer the

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Steve Martinelli wrote: > So it's only for this time around (Mitaka-1) that I'll have to tag bugs > as fix-released, because the release automation will just leave a comment? We'll likely turn all FixCommitted bugs to FixReleased (one last time) as part of the transition, so you don't really need

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Excerpts from Armando M.'s message of 2015-11-23 17:37:47 -0800: > On 23 November 2015 at 13:58, Doug Hellmann wrote: > > > As part of completing the release automation work and deprecating our > > use of Launchpad for release content tracking, we also want make some > >

Re: [openstack-dev] [release] process change for closing bugs when patches merge

On 23/11/15 16:58 -0500, Doug Hellmann wrote: As part of completing the release automation work and deprecating our use of Launchpad for release content tracking, we also want make some changes to the way patches associated with bugs are handled. Right now, when a patch with Closes-Bug in the

Re: [openstack-dev] [release] process change for closing bugs when patches merge

On 24 November 2015 at 10:58, Doug Hellmann wrote: > As part of completing the release automation work and deprecating our > use of Launchpad for release content tracking, we also want make some > changes to the way patches associated with bugs are handled. > > Right now,

[openstack-dev] [release] process change for closing bugs when patches merge

As part of completing the release automation work and deprecating our use of Launchpad for release content tracking, we also want make some changes to the way patches associated with bugs are handled. Right now, when a patch with Closes-Bug in the commit message merges, the bug status is updated

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Martinelli OpenStack Keystone Project Team Lead From: Doug Hellmann <d...@doughellmann.com> To: openstack-dev <openstack-dev@lists.openstack.org> Date: 2015/11/23 05:00 PM Subject: [openstack-dev] [release] process change for closing bugs when patches merg

Re: [openstack-dev] [release] process change for closing bugs when patches merge

On 23 November 2015 at 13:58, Doug Hellmann wrote: > As part of completing the release automation work and deprecating our > use of Launchpad for release content tracking, we also want make some > changes to the way patches associated with bugs are handled. > > Right now,