On Mon, Feb 9, 2015 at 3:10 PM, Alan Pevec <ape...@gmail.com> wrote: > >> >> Tracking etherpad: > >> >> https://etherpad.openstack.org/p/wedged-stable-gate-feb-2015 > > BTW there is a tracking etherpad updated by > https://wiki.openstack.org/wiki/StableBranch#Stable_branch_champions > https://etherpad.openstack.org/p/stable-tracker > linked in https://wiki.openstack.org/wiki/StableBranch#Gate_Status and > announced on this list > http://lists.openstack.org/pipermail/openstack-dev/2015-January/054444.html > > From crossed items in "Recently closed" section you can see that > branch champions have been busy. > > There are two main audiences for stable branches:
* Downstream consumers. * Upstream developers working on master who need a working stable branch. I cannot comment on how well the first group is being supported. But as a member of the second group, I am constantly frustrated by how frequently broken stable branches ruin my day. > > You are missing the fact that a bunch of us (Matt Treinish, myself and > > others) are frustrated by the fact that we end up fixing stable branches > > whenever they break because we touch tempest, grenade and other projects > > that require working stable branches. But we do not want to be working on > > stable branches ourselves. I begrudgingly stepped up to work on pinning > all > > requirements on stable branches, to reduce the number of times stable > > branches break and ruin my day. But my plan to cap dependencies has been > > delayed several times by stable branches breaking again and again, along > > with unwinding undesired behaviors in our testing harnesses. > > > > Most recently, stable/juno grenade broke on February 4th (due to the > release > > of tempest-lib 0.2.0). This caused bug > > So that's a change in tooling, not stable branch itself. Idea when 15 > months for Icehouse was discussed was that branchless Tempest would > make it easier, but now it turns out that's making both tooling and > stable branch unhappy. > I don't think its reasonable to assume maintaining the stable/branch excludes actively supporting and improving are testing harness and related tooling. Our tooling is constantly changing and supporting stable branches means working on our tooling to make sure its functioning as expected for stable branches. Also cutting a new release of a library is not a 'change in tooling'. > > What I expect to happen when issues like this arise is interested parties > > work together to fix things and be proactive and make stable testing more > > robust. Instead we currently have people who have no desire to work on > > stable branches maintaining them. > > At least parts of stable team have been pro-active (see above > etherpad) but I guess we have a communication issue here: has > anyonetried to contact stable branch champions (juno=Adam, > icehouse=Ihar) and what exactly do you expect stable team to do? > AFAICT these are all changes in tooling where stable-maint is not core > (devstack, tempest)... > Where is it documented that Adam is the Juno branch champion and Ihar is Icehouse's? I didn't see it anywhere in the wiki. If something breaks in stable/juno and grenade on master seizes up, what should we do? When issues are blocking development we should not have to wait for any one person to respond -- single points of failure are bad. So I don't think 'has anyone tried to contact us' is the right question to ask. A better question to ask is 'have stable branches recently prevented development' So who should I contact to help me freeze all stable/* dependencies? Or better yet, someone to drive the effort instead. > BTW Icehouse 2014.1.4 was planned[*] for Feb 19 with freeze starting > on Feb 12, I'll delay it for now until we sort the current situation > out. > > > Cheers, > Alan > > > [*] > https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Ficehouse_releases > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
