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.