Hi folks! Does it possible to store history of the project without alignment to OpenStack releases?
2017-04-19 17:54 GMT+03:00 Jimmy McArthur <[email protected]>: > Ideally, as far back as your project goes. That way we will have a > complete API history, per release, on the project navigator. This also > helps us determine the project age. > > Thanks! > Jimmy > > Telles Nobrega <[email protected]> > April 19, 2017 at 9:48 AM > Hi Monty, > > quick question, how far into past releases should we go? > > Thanks, > > -- > > TELLES NOBREGA > > SOFTWARE ENGINEER > > Red Hat I <https://www.redhat.com/> > > [email protected] > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Monty Taylor <[email protected]> > April 18, 2017 at 3:03 PM > Hey everybody! > > The Foundation is rolling out a new version of the Project Navigator. One > of the things it contains is a section that shows API versions available > for each project for each release. They asked the TC's help in providing > that data, so we spun up a new repository: > > http://git.openstack.org/cgit/openstack/project-navigator-data > > that the Project Navigator will consume. > > We need your help! > > The repo contains a file for each project for each release with > CURRENT/SUPPORTED/DEPRECATED major versions and also microversion ranges if > they exist. The data is pretty much exactly what everyone already produces > in their version discovery documents - although it's normalized into the > format described by the API-WG: > > > https://specs.openstack.org/openstack/api-wg/guidelines/ > microversion_specification.html#version-discovery > > What would be really helpful is if someone from each project could go make > a patch to the repo adding the historical (and currently) info for your > project. We'll come up with a process for maintaining it over time - but > for now just crowdsourcing the data seems like the best way. > > The README file explains the format, and there is data from a few of the > projects for Newton. > > It would be great to include an entry for every release - which for many > projects will just be the same content copied a bunch of times back to the > first release the project was part of OpenStack. > > This is only needed for service projects (something that registers in the > keystone catalog) and is only needed for 'main' APIs (like, it is not > needed, for now, to put in things like Placement) > > If y'all could help - it would be super great! > > Thanks! > Monty > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Best regards, Andrey Kurilin.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
