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

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 : > Sweet - so - each repo should have release and component (if I understand > those right) - is there

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

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,

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

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

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

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