Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-24 Thread Tony Breeds
On Fri, Jun 24, 2016 at 08:44:25AM +0200, Haïkel wrote: > Roger. Who's Roger? > Maybe we can put it at the agenda to the next (or later) meeting to > work on specifications > and define the next steps before moving on. Yup sounds like a good plan. LIke I said it's a pause not a complete

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-24 Thread Haïkel
2016-06-24 4:02 GMT+02:00 Tony Breeds : > > I think we need to pause on these 'normalizing' changes in g-r. They're > genertaing whitspace only reviews in many, (possibly all) projects that have > managed requirements. > > We need to do more testing and possibly make the

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-23 Thread Tony Breeds
On Wed, Jun 22, 2016 at 03:23:43PM +1000, Tony Breeds wrote: > On Wed, Jun 22, 2016 at 06:45:31AM +0200, Haïkel wrote: > > Hi, > > > > as a packager, I spend a lot of time to scrutinize the requirements > > repo, and I find it easier to read if specifiers are ordered. > > So in a quick glance,

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-22 Thread Sean Dague
On 06/22/2016 01:36 AM, Haïkel wrote: > 2016-06-22 7:23 GMT+02:00 Tony Breeds : >> >> I'm fine with doign something like this. I wrote [1] some time ago but >> didn't >> push on it as I needed to verify that this wouldn't create a "storm" of >> pointless updates that

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-21 Thread Haïkel
2016-06-22 7:23 GMT+02:00 Tony Breeds : > > I'm fine with doign something like this. I wrote [1] some time ago but didn't > push on it as I needed to verify that this wouldn't create a "storm" of > pointless updates that just reorder things in every projects >

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-21 Thread Tony Breeds
On Wed, Jun 22, 2016 at 06:45:31AM +0200, Haïkel wrote: > Hi, > > as a packager, I spend a lot of time to scrutinize the requirements > repo, and I find it easier to read if specifiers are ordered. > So in a quick glance, you can check which is the min version required > and max one without

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-21 Thread Swapnil Kulkarni (coolsvap)
On Wed, Jun 22, 2016 at 10:15 AM, Haïkel wrote: > Hi, > > as a packager, I spend a lot of time to scrutinize the requirements > repo, and I find it easier to read if specifiers are ordered. > So in a quick glance, you can check which is the min version required > and

[openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-21 Thread Haïkel
Hi, as a packager, I spend a lot of time to scrutinize the requirements repo, and I find it easier to read if specifiers are ordered. So in a quick glance, you can check which is the min version required and max one without trying to search them among other specifiers. I scripted a basic linter