openstack
/
tacker-specs
Code Issues Proposed changes
NFV Orchestration (Tacker) Specifications
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
310 Commits
1 Branch
0 Tags
16 MiB
Python 100%
 
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '949c4ce423'
${ noResults }
Go to file
Yasufumi Ogawa 949c4ce423 Add 2023.1 specs directory 
Using release number here. In Zed cycle, TC passed a resolution[1] and
updated the release Identification document[2] 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.

[1] https://governance.openstack.org/tc/resolutions/20220524-release-identification-process.html
[2] https://governance.openstack.org/tc/reference/release-naming.html

Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Change-Id: I9c56ef2a1bbce716a37cac83e4316e37d989b386
 		8 months ago
doc Add 2023.1 specs directory 8 months ago
specs Add 2023.1 specs directory 8 months ago
.gitignore Remove testr 2 years ago
.gitreview OpenDev Migration Patch 4 years ago
.zuul.yaml import zuul job settings from project-config 5 years ago
LICENSE Add base tacker-specs framework 9 years ago
README.rst Change tacker-specs webpage from oslosphinx to openstackdocstheme 5 years ago
setup.cfg setup.cfg: Replace dashes with underscores 2 years ago
setup.py Add base tacker-specs framework 9 years ago
test-requirements.txt Refactor and clean up specs dir 5 years ago
tox.ini Update min version of tox 2 years ago

README.rst

Team and repository tags

image

OpenStack Tacker Specifications

This git repository is used to hold approved design specifications for additions to the Tacker 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 layout of this repository is:

specs/<release>/

You can find an example spec in specs/template.rst.

Specifications are proposed for a given release by adding them to the specs/<release> 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.

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.

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:

https://wiki.openstack.org/wiki/Blueprints

Launchpad blueprints for Tacker can be found at:

https://blueprints.launchpad.net/tacker

For more information about working with gerrit, see:

https://docs.openstack.org/infra/manual/developers.html#development-workflow

To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:

$ tox

After running 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.