2012/11/22 Thierry Carrez <thie...@openstack.org>: > It's more a question of how disruptive the patch is vs. how critical the > bug is. Given how annoying this bug is, it would be good to at least > assess the disruption factor of a backport. > > Did we identify the bug number (or commit id) of the Folsom fix, so that > we can open an Essex task for it ?
That's exactly what I'm saying, you need someone to do all of this (asses risk/benefit, find master fix and backport it, eventually make a new stable release) and currently only Dave Walker signed up for this work: https://launchpad.net/~openstack-essex-maint/+members Cheers, Alan _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
