[openstack-dev] Solving the client libs stable support dilemma

2014-11-15 Thread Jeremy Stanley
During the Kilo design summit session on Oslo versioning changes, we mostly resolved to switch to semver without alphas and pin stable branch libs to less than the next nontrivial version number (allowing for backports to fix bugs with subsequent point releases on a stable branch when needed). This

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Robert Collins
On 16 November 2014 09:06, Robert Collins wrote: > On 16 November 2014 03:25, Sean Dague wrote: >> Testtools 1.2.0 release apparently broke subunit.run discover --list >> which breaks the way that tempest calls the test chain. No tempest runs >> have passed since it's release. ... > I think every

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Dave Walker
On 15 November 2014 21:22, Jeremy Stanley wrote: > On 2014-11-15 20:38:02 + (+), Dave Walker wrote: >> You are right, I accidently folded two issues into 1. However, I do >> not understand how we can resolve this issue the way you have outlined >> without introducing a new minimum version

Re: [openstack-dev] [oslo] updated release instructions

2014-11-15 Thread Davanum Srinivas
Doug, I can help with oslo library releases this cycle. thanks, dims On Fri, Nov 14, 2014 at 10:23 AM, Doug Hellmann wrote: > Last cycle Thierry put together a tool to make releasing Oslo libraries > easier for us. Using the tool will ensure that all of our releases are > tracked consistently

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Jeremy Stanley
On 2014-11-15 20:38:02 + (+), Dave Walker wrote: > You are right, I accidently folded two issues into 1. However, I do > not understand how we can resolve this issue the way you have outlined > without introducing a new minimum version on unittest2, which was not > previously a requirement

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Robert Collins
On 16 November 2014 09:38, Dave Walker wrote: > On 15 November 2014 20:23, Robert Collins wrote: >> On 16 November 2014 09:03, Dave Walker wrote: >>> On 15 November 2014 19:51, Robert Collins wrote: It probably needs to be backed out of stable/icehouse. The issue is that we were insta

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Dave Walker
On 15 November 2014 20:23, Robert Collins wrote: > On 16 November 2014 09:03, Dave Walker wrote: >> On 15 November 2014 19:51, Robert Collins wrote: >>> It probably needs to be backed out of stable/icehouse. The issue is >>> that we were installing unittest2 via distro packages *and* testtools >

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Robert Collins
On 16 November 2014 09:03, Dave Walker wrote: > On 15 November 2014 19:51, Robert Collins wrote: >> It probably needs to be backed out of stable/icehouse. The issue is >> that we were installing unittest2 via distro packages *and* testtools >> new dependency on unittest2 did not express a minimum

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Robert Collins
On 16 November 2014 03:25, Sean Dague wrote: > Testtools 1.2.0 release apparently broke subunit.run discover --list > which breaks the way that tempest calls the test chain. No tempest runs > have passed since it's release. > > https://review.openstack.org/#/c/134705/ is a requirements pin, though

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Jeremy Stanley
On 2014-11-16 08:51:34 +1300 (+1300), Robert Collins wrote: [...] > The issue is that we were installing unittest2 via distro packages > *and* testtools new dependency on unittest2 did not express a > minimum version. [...] BTW, patches to stop installing unittest2 from distro packages in devstack

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Dave Walker
On 15 November 2014 19:51, Robert Collins wrote: > It probably needs to be backed out of stable/icehouse. The issue is > that we were installing unittest2 via distro packages *and* testtools > new dependency on unittest2 did not express a minimum version. > > We're just about to issue 1.2.1 which

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Robert Collins
It probably needs to be backed out of stable/icehouse. The issue is that we were installing unittest2 via distro packages *and* testtools new dependency on unittest2 did not express a minimum version. We're just about to issue 1.2.1 which will have such a minimum version. And for the record, this

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Dave Walker
On 15 November 2014 14:25, Sean Dague wrote: > Testtools 1.2.0 release apparently broke subunit.run discover --list > which breaks the way that tempest calls the test chain. No tempest runs > have passed since it's release. > > https://review.openstack.org/#/c/134705/ is a requirements pin, though

Re: [openstack-dev] [all] A more dynamic wiki, introducing Categories

2014-11-15 Thread Jeremy Stanley
On 2014-11-15 16:37:50 +0100 (+0100), Stefano Maffulli wrote: [...] > If you don't create the New_Category page, it will end up in the > 'wantedCategories' special page: > > https://wiki.openstack.org/wiki/Special:WantedCategories [...] Oh, neat! This is a new feature. In older* versions it just

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Jeremy Stanley
On 2014-11-15 09:25:54 -0500 (-0500), Sean Dague wrote: > Testtools 1.2.0 release apparently broke subunit.run discover --list [...] > Also... lets try not to release libraries on Fridays before disappearing > for the weekend... please. Pretty please. Also reported upstream as https://github.com/t

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Davanum Srinivas
Sean, I can baby sit these 3 thanks, dims On Sat, Nov 15, 2014 at 9:25 AM, Sean Dague wrote: > Testtools 1.2.0 release apparently broke subunit.run discover --list > which breaks the way that tempest calls the test chain. No tempest runs > have passed since it's release. > > https://review.open

Re: [openstack-dev] [all] A more dynamic wiki, introducing Categories

2014-11-15 Thread Stefano Maffulli
On 11/14/2014 09:11 PM, Jeremy Stanley wrote: > Categories emerge automatically as you tag pages into them. No > separate category creation step is required. True although incomplete. Categories are just pages, like almost anything in mediawiki, so if you add text [[Category: New_Category]] in a p

[openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 Thread Sean Dague
Testtools 1.2.0 release apparently broke subunit.run discover --list which breaks the way that tempest calls the test chain. No tempest runs have passed since it's release. https://review.openstack.org/#/c/134705/ is a requirements pin, though I think because of grenade this is actually going to h

Re: [openstack-dev] TC election by the numbers

2014-11-15 Thread Eoghan Glynn
> It's certainly not a fun thing to do (trying to guide a > community of disjoint folks) and it likely comes with little > recognition when successful, but IMHO we surely need more of > this active technical leadership vs. blessing of projects; of > course the boundary between being a engaging lea

Re: [openstack-dev] TC election by the numbers

2014-11-15 Thread Eoghan Glynn
> >> 1. *make a minor concession to proportionality* - while keeping the > >> focus on consensus, e.g. by adopting the proportional Condorcet > >> variant. > > > > It would be interesting to see the analysis again, but in the past this > > proved to not make much difference. > > For t

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

2014-11-15 Thread Martin Geisler
Gabriel Hurley writes: Hi Gabriel, > As the former Horizon PTL, I have a great respect for the importance > of the contributions the distro maintainers/developers make to Horizon > and OpenStack as a whole. From how many bugs the distros manage to > find, to their diligence in vetting the softwa