- Openstack-stable-maint - lists.openstack.org

Jenkins build is back to normal : periodic-tempest-devstack-vm-stable-diablo #81
by OpenStack Jenkins 08 Nov '12

08 Nov '12

See <https://jenkins.openstack.org/job/periodic-tempest-devstack-vm-stable-diabl…>

1 0

Proposed RPC API change on nova stable/folsom
by Mark McLoughlin 01 Nov '12

01 Nov '12

Hey, For the first time (that I'm aware of) we have a request to include a backport on the stable branch which includes a change to the RPC API: https://review.openstack.org/14754 This is troublesome for a couple of reasons: 1) People upgrading to a version which includes this change would need to be aware that they should update their compute services before updating their API services 2) While in this case we're backporting the first RPC API change since Folsom (i.e. version 2.2 was in Folsom, this is version 2.3) if we were backporting a later API version we would have to give up on retaining Folsom compatibility in Grizzly In this particular case, I'm somewhat hopeful we might be able to figure out a fix which doesn't involve the API change but that remains to be seen. Any ideas? Cheers, Mark.

2 2

stable-maint
by Mark McLoughlin 01 Nov '12

01 Nov '12

Hi Gabriel, The openstack-stable-maint team is responsible for the stable/folsom branch. That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here: http://wiki.openstack.org/StableBranch During Essex, I added all the PTLs to the team since they have to make similar tradeoffs when backporting to the milestone-proposed branch. Since you've taken over from Devin as Horizon PTL, I figure it makes sense to add you in place of Devin. So, basically - keep an eye out for changes proposed to stable/folsom and then: * evaluate risk of a patch * consider how severe the issue is for users * check that it's already fixed on master Please add a little comment indicating whether a change meets those criteria when adding your +/-2 Also, stable/folsom reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member. Cheers, Mark.

1 0

stable-maint
by Mark McLoughlin 01 Nov '12

01 Nov '12

Hi John, Now that Cinder is core, the openstack-stable-maint team is responsible for the stable/folsom branch. That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here: http://wiki.openstack.org/StableBranch During Essex, I added all the PTLs to the team since they have to make similar tradeoffs when backporting to the milestone-proposed branch. That has worked well, so I figure it makes sense to continue it. So, basically - keep an eye out for changes proposed to stable/folsom and then: * evaluate risk of a patch * consider how severe the issue is for users * check that it's already fixed on master Please add a little comment indicating whether a change meets those criteria when adding your +/-2 Also, stable/folsom reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member. Cheers, Mark.

1 0