In Zed cycle, TC passed a resolution and updated the release Identification document to use the release number as primary identifier in the development cycle. Release name will be used in marketting and release team tooling (until they are migrated to work with release number) only. Let's use release number consistently across OpenStack projects.  https://governance.openstack.org/tc/resolutions/20220524-release-identification-process.html  https://governance.openstack.org/tc/reference/release-naming.html Change-Id: I513c4ebca38984b80d8e5613c3190d88fcb44aca
|5 months ago|
|doc||5 months ago|
|priorities||5 months ago|
|specs||5 months ago|
|tests||7 years ago|
|.gitignore||5 years ago|
|.gitreview||4 years ago|
|.stestr.conf||5 years ago|
|.zuul.yaml||3 years ago|
|LICENSE||9 years ago|
|README.rst||5 years ago|
|bindep.txt||3 years ago|
|requirements.txt||3 years ago|
|tox.ini||10 months ago|
Team and repository tags
OpenStack Glance Specifications
This git repository is used to hold approved design specifications for additions to the Glance project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.
The general layout of this repository is:
You can find an example spec in specs/template.rst.
Beginning with the Mitaka release, there is a further subdivision into:
A specification is proposed for a given release by adding it to the specs/<release>/approved directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.
When a feature has been completed, its specification will be moved to the 'implemented' directory for the release in which it was implemented.
Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.
Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:
Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:
For more information about working with gerrit, see:
To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
tox, the documentation will be available for viewing in HTML format in the
doc/build/ directory. Please do not checkin the generated HTML files as a part of your commit.