Hi, I have backported all of the available neutron patches - rest of patches are either pending review or some TLC on master: https://review.openstack.org/#/c/39167/ https://review.openstack.org/#/c/39168/ https://review.openstack.org/#/c/39227/ https://review.openstack.org/#/c/39266/ Thanks Gary

-----Original Message----- From: Gary Kotton [mailto:gkotton@vmware.com] Sent: Tuesday, July 30, 2013 12:12 AM To: Adam Gandelman; openstack-stable-maint@lists.openstack.org Cc: Alan Pevec Subject: Re: [Openstack-stable-maint] 2013.1.3 Status Check

Hi, Tomorrow I will deal with the Neutron backports. Thanks Gary

-----Original Message----- From: Adam Gandelman [mailto:adamg@canonical.com] Sent: Monday, July 29, 2013 9:24 PM To: openstack-stable-maint@lists.openstack.org Cc: Alan Pevec Subject: [Openstack-stable-maint] 2013.1.3 Status Check

Hey All-

We're quickly approaching 2013.1.3 release on Thurs Aug 08. I assume we'll be freezing stable/grizzly the branches this Thurs Aug 01 in preparation for next week's release. The review queue for the stable branches looks okay ATM, with most Critical bugs fixed. A few things as we move closer to freeze:

- Are any projects outside of core expecting a stable release? Ceilometer, heat, etc?

- The neutron branch has been pretty quiet. There are a number of bugs tagged, but not much being proposed for merge.

Lastly, I'd like to bring attention to two bugs that could use some discussion on the list. Both fixes can be perceived as introducing new features, but folks are passionate about landing them in 2013.1.2:

(cinder) solidfire: Add ability to override account prefix https://review.openstack.org/#/c/35406/ http://pad.lv/1179671

(nova) VNC console does not work with VCDriver https://review.openstack.org/#/c/38473/ http://pad.lv/1178369

These fixes seem to be driven by the needs of real customers with real deployments, and are both are isolated to the respective drivers. I'm personally in favor of granting a policy exception on these if it prevents deployers from rolling out with their own patches. What do others think?

Thanks, Adam

_______________________________________________ Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint

_______________________________________________ Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint

There is one that slipped under our radar -

https://bugs.launchpad.net/nova/+bug/1172177. I have backported this - https://review.openstack.org/#/c/40058/

That one is a good exception candidate, any objections from stable-maint members?

Cheers, Alan

On 3 August 2013 20:35, Adam Gandleman adamg@canonical.com wrote:

On 08/03/2013 12:31 PM, Alan Pevec wrote:

...

That one is a good exception candidate, any objections from stable-maint members?

+1

Annndd. +2'd.. Should be merging now.

Thanks.

...

There is one that slipped under our radar - https://bugs.launchpad.net/nova/+bug/1172177. I have backported this - https://review.openstack.org/#/c/40058/

There were few more other exceptions after freeze:

- Neutron, CISCO driver https://review.openstack.org/40011 * already merged

- Neutron, https://review.openstack.org/40104 "The other of two patches that fixes bug #1194438" * Mark, is this stable freeze exception candidate?

- Keystone (proposed) https://review.openstack.org/34622 * Dolph, is this stable freeze exception candidate? NB review 34622 has wrong change-id

- Heat (not part of the integrated release, but stable-maint is helping Heat team to prepare Heat 2013.1.3 release) https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:s... * 3 waiting for 2nd +2 * https://review.openstack.org/39380 is work-in-progress, Steve, is this going to make 2013.1.3 ?

Any opinion from stable-maint?

Cheers, Alan

2013/8/5 Dolph Mathews dolph.mathews@gmail.com:

...

• Keystone (proposed) https://review.openstack.org/34622
  • Dolph, is this stable freeze exception candidate? NB review 34622

has wrong change-id

Gabriel described the issue as "exceedingly annoying" which I think is quite accurate. The patch to keystone itself is just a delete, merged to master 2 months ago, and hasn't resulted in any new issues. While it's not a game breaker, I think it'd be a welcome addition in stable/grizzly.

ok, I've cherry picked with original change-id https://review.openstack.org/40249 Please review after Jenkins verifies it.

Cheers, Alan