Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Excerpts from Lingxian Kong's message of 2015-11-09 15:00:25 +0800: > On Wed, Nov 4, 2015 at 3:46 AM, Doug Hellmann wrote: > > 1. We need one patch to the master branch of the project to add the > >instructions for publishing the notes as part of the project > >

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Excerpts from Andreas Jaeger's message of 2015-11-07 16:42:40 +0100: > On 11/03/2015 08:46 PM, Doug Hellmann wrote: > > [...] > > We are ready to start rolling out Reno for use with Liberty stable > > branch releases and in master for the Mitaka release. We need the > > release liaisons to create

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Excerpts from Doug Hellmann's message of 2015-11-03 14:46:04 -0500: > As we discussed at the summit, the release management team is > modifying our change management tracking tools and processes this > cycle. This email is the official announcement of those changes, > with more detail than we

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Excerpts from Andreas Jaeger's message of 2015-11-09 10:11:33 +0100: > On 11/03/2015 08:46 PM, Doug Hellmann wrote: > > As we discussed at the summit, the release management team is > > modifying our change management tracking tools and processes this > > cycle. This email is the official

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Excerpts from Doug Hellmann's message of 2015-11-03 14:46:04 -0500: > As we discussed at the summit, the release management team is > modifying our change management tracking tools and processes this > cycle. This email is the official announcement of those changes, > with more detail than we

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

On 11/03/2015 08:46 PM, Doug Hellmann wrote: As we discussed at the summit, the release management team is modifying our change management tracking tools and processes this cycle. This email is the official announcement of those changes, with more detail than we provided at the summit. In past

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

On Wed, Nov 4, 2015 at 3:46 AM, Doug Hellmann wrote: > 1. We need one patch to the master branch of the project to add the >instructions for publishing the notes as part of the project >sphinx documentation build. An example patch for Glance is in >[2]. > Hi,

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

On 11/03/2015 08:46 PM, Doug Hellmann wrote: [...] We are ready to start rolling out Reno for use with Liberty stable branch releases and in master for the Mitaka release. We need the release liaisons to create and merge a few patches for each project between now and the Mitaka-1 milestone. 1.

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Excerpts from Louis Taylor's message of 2015-11-04 08:05:44 +: > On Wed, Nov 04, 2015 at 03:03:29PM +1300, Fei Long Wang wrote: > > Hi Doug, > > > > Thanks for posting this. I'm working on this for Zaqar now and there is a > > question. As for the stable/liberty patch, where does the

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

On Wed, Nov 04, 2015 at 03:03:29PM +1300, Fei Long Wang wrote: > Hi Doug, > > Thanks for posting this. I'm working on this for Zaqar now and there is a > question. As for the stable/liberty patch, where does the "60fdcaba00e30d02" > in [1] come from? Thanks. > > [1] >

[openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

As we discussed at the summit, the release management team is modifying our change management tracking tools and processes this cycle. This email is the official announcement of those changes, with more detail than we provided at the summit. In past cycles, we have used a combination of Launchpad

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Hi Doug, Thanks for posting this. I'm working on this for Zaqar now and there is a question. As for the stable/liberty patch, where does the "60fdcaba00e30d02" in [1] come from? Thanks. [1] https://review.openstack.org/#/c/241322/1/releasenotes/notes/60fdcaba00e30d02-start-using-reno.yaml