[openstack-dev] [tc] project-navigator-data repo live - two choices need input

Sebastian Marcet smarcet at gmail.com
Tue Apr 11 14:58:12 UTC 2017


i think that we the format proposed on
https://review.openstack.org/#/c/454691/1
we would be ok
giving my +1 there

cheers


2017-04-11 10:45 GMT-03:00 Monty Taylor <mordred at inaugust.com>:

> Sweet - so - each repo should have release and component (if I understand
> those right) - is there additional info that we should include?
>
> Like - in the multi-file approach, it's a set of directories with files of
> the form:
>
> release/component.json -> contains versions[]
>
> And the single file, it's:
>
> release/{release}.json -> contains services[] each with versions[]
>
> On 04/11/2017 07:40 AM, Sebastian Marcet wrote:
>
>> Monty thx so much
>> basically we have following structure
>>
>> Release ----->Component ----->Version
>>
>> so i think that we could consume this pretty easily, only caveat is that
>> we still to add from our side, Release and Component data, but i guess
>> that is doable
>>
>> thx u so much !!! i will take a look to both formats
>>
>> cheers
>>
>> 2017-04-11 8:44 GMT-03:00 Monty Taylor <mordred at inaugust.com
>> <mailto:mordred at inaugust.com>>:
>>
>>     Hey all,
>>
>>     We've got the project-navigator-data repo created and there are two
>>     proposals up for what the content should look like.
>>
>>     Could TC folks please add openstack/project-navigator-data to your
>>     watch lists, and go review:
>>
>>     https://review.openstack.org/#/c/454688
>>     <https://review.openstack.org/#/c/454688>
>>     https://review.openstack.org/#/c/454691
>>     <https://review.openstack.org/#/c/454691>
>>
>>     so we can come to an agreement on which version we prefer? Maybe
>>     just +2 the one you prefer (or both if you don't care) and only -1
>>     if you specifically dislike one over the other?
>>
>>     Thanks!
>>     Monty
>>
>>     ____________________________________________________________
>> ______________
>>     OpenStack Development Mailing List (not for usage questions)
>>     Unsubscribe:
>>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
>> >
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>
>>
>>
>>
>> --
>> Sebastian Marcet
>> https://ar.linkedin.com/in/smarcet
>> SKYPE: sebastian.marcet
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Sebastian Marcet
https://ar.linkedin.com/in/smarcet
SKYPE: sebastian.marcet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170411/34e685ee/attachment.html>


More information about the OpenStack-dev mailing list