Re: [openstack-dev] [tc] version document for project navigator

2017-04-18 Thread Jimmy McArthur
Thank you, sir! :) Monty Taylor April 18, 2017 at 3:38 PM I just sent out the email requesting folks send in patches. Maybe we'll get a flood of them now ... __ OpenStack Development

Re: [openstack-dev] [tc] version document for project navigator

2017-04-18 Thread Monty Taylor
I just sent out the email requesting folks send in patches. Maybe we'll get a flood of them now ... On 04/18/2017 08:46 AM, Jimmy McArthur wrote: All, we have modified our ingest tasks to look for this new data. Can we get an ETA on when to expect updates from the majority of projects? Right

Re: [openstack-dev] [tc] version document for project navigator

2017-04-18 Thread Jimmy McArthur
All, we have modified our ingest tasks to look for this new data. Can we get an ETA on when to expect updates from the majority of projects? Right now, there isn't too much to test with. Cheers, Jimmy Thierry Carrez April 14, 2017 at 3:21 AM OK approved. Doug

Re: [openstack-dev] [tc] version document for project navigator

2017-04-14 Thread Thierry Carrez
Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2017-04-13 18:03:41 +0200: >> Monty Taylor wrote: >>> On 04/13/2017 08:28 AM, Jimmy McArthur wrote: Just checking on the progress of this. :) >>> >>> Unfortunately a good portion of the TC was away this week at the >>>

Re: [openstack-dev] [tc] version document for project navigator

2017-04-13 Thread Doug Hellmann
Excerpts from Thierry Carrez's message of 2017-04-13 18:03:41 +0200: > Monty Taylor wrote: > > On 04/13/2017 08:28 AM, Jimmy McArthur wrote: > >> Just checking on the progress of this. :) > > > > Unfortunately a good portion of the TC was away this week at the > > leadership training so getting a

Re: [openstack-dev] [tc] version document for project navigator

2017-04-13 Thread Thierry Carrez
Monty Taylor wrote: > On 04/13/2017 08:28 AM, Jimmy McArthur wrote: >> Just checking on the progress of this. :) > > Unfortunately a good portion of the TC was away this week at the > leadership training so getting a final ok on it was a bit stalled. It's > seeming like the multi-file version is

Re: [openstack-dev] [tc] version document for project navigator

2017-04-13 Thread Monty Taylor
On 04/13/2017 08:28 AM, Jimmy McArthur wrote: Just checking on the progress of this. :) Unfortunately a good portion of the TC was away this week at the leadership training so getting a final ok on it was a bit stalled. It's seeming like the multi-file version is the one most people like

Re: [openstack-dev] [tc] version document for project navigator

2017-04-13 Thread Jimmy McArthur
Just checking on the progress of this. :) Monty Taylor April 7, 2017 at 7:05 AM There is a new repo now: http://git.openstack.org/cgit/openstack/project-navigator-data I have pushed up two different patches with two different approaches:

Re: [openstack-dev] [tc] version document for project navigator

2017-04-07 Thread Monty Taylor
On 04/06/2017 03:51 PM, Jimmy McArthur wrote: Cool. Thanks Monty! Monty Taylor April 6, 2017 at 3:21 PM On 04/06/2017 11:58 AM, Jimmy McArthur wrote: Assuming this format is accepted, do you all have any sense of when this data will be complete for all projects?

Re: [openstack-dev] [tc] version document for project navigator

2017-04-06 Thread Jimmy McArthur
Cool. Thanks Monty! Monty Taylor April 6, 2017 at 3:21 PM On 04/06/2017 11:58 AM, Jimmy McArthur wrote: Assuming this format is accepted, do you all have any sense of when this data will be complete for all projects? Hopefully "soon" :) Honestly, it's not

Re: [openstack-dev] [tc] version document for project navigator

2017-04-06 Thread Monty Taylor
On 04/06/2017 11:58 AM, Jimmy McArthur wrote: Assuming this format is accepted, do you all have any sense of when this data will be complete for all projects? Hopefully "soon" :) Honestly, it's not terribly difficult data to produce, so once we're happy with it and where it goes,

Re: [openstack-dev] [tc] version document for project navigator

2017-04-06 Thread Jimmy McArthur
Assuming this format is accepted, do you all have any sense of when this data will be complete for all projects? Jimmy McArthur April 5, 2017 at 8:59 AM FWIW, from my perspective on the Project Navigator side, this format works great. We can actually derive the

Re: [openstack-dev] [tc] version document for project navigator

2017-04-05 Thread Jimmy McArthur
FWIW, from my perspective on the Project Navigator side, this format works great. We can actually derive the age of the project from this information as well by identifying the first release that has API data for a particular project. I'm indifferent about where it lives, so I'd defer to you

Re: [openstack-dev] [tc] version document for project navigator

2017-04-05 Thread Thierry Carrez
Monty Taylor wrote: > As per our discussion in today's TC meeting, I have made a document > format for reporting versions to the project navigator. I stuck it in > the releases repo: > > https://review.openstack.org/453361 > > Because there was already per-release information there, and the >

Re: [openstack-dev] [tc] version document for project navigator

2017-04-04 Thread Jimmy McArthur
Hooray! Thanks Monty :) Monty Taylor April 4, 2017 at 5:47 PM Hey all, As per our discussion in today's TC meeting, I have made a document format for reporting versions to the project navigator. I stuck it in the releases repo:

[openstack-dev] [tc] version document for project navigator

2017-04-04 Thread Monty Taylor
Hey all, As per our discussion in today's TC meeting, I have made a document format for reporting versions to the project navigator. I stuck it in the releases repo: https://review.openstack.org/453361 Because there was already per-release information there, and the governance repo did