59eda7f2a4
We want to default to running all tox environments under python 3, so set the basepython value in each environment. We do not want to specify a minor version number, because we do not want to have to update the file every time we upgrade python. We do not want to set the override once in testenv, because that breaks the more specific versions used in default environments like py35 and py36. Change-Id: If134cb43df5b974c1cbd2415b144f6805d37893a Signed-off-by: Doug Hellmann <doug@doughellmann.com> |
||
|---|---|---|
| doc/source | ||
| specs | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| template.rst | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
OpenStack I18n Specifications
This git repository is used to keep track of design specifications with reviews and changes to the OpenStack I18n program. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to openstack/i18n repository.
Expected Work Flow
- Create a blueprint in https://blueprints.launchpad.net/openstack-i18n
with a task affecting the
i18n-specsproject. - Propose a change to i18n-specs repository. You can find an example spec in /template.rst. Fill it and create a .rst file in /specs/ directory with the details of the new blueprint (ensure "Implements: blueprint [blueprint name]" is in the commit message).
- Review happens on proposal by i18n-core members and others.
- When ready for final approval, bring forward the proposed item to the i18n IRC meeting or mailing list: openstack-i18n@lists.openstack.org.
Once a specification is approved...
- Leave a comment to the git address of the specification on the blueprint.
- Indicate "Implements: blueprint [blueprint name]" on the commit messages for related implementations.
For i18n, blueprints are required for larger, cross- and coordinated projects but not for small translation fixes. It's a judgement call for whether you need a spec, so feel free to ask in the #openstack-i18n IRC channel or on the openstack-i18n mailing list.
Prior to the Ocata development cycle, this repository was not used for spec reviews. Reviews prior to Ocata were completed mainly through Launchpad blueprints.
Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see https://wiki.openstack.org/wiki/Blueprints.
For more information about working with gerrit, see http://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:
$ toxAfter running tox, the documentation will be available
for viewing in HTML format in the doc/build/ directory.
Please do not check in the generated HTML files as a part of your
commit.
The files are published at http://specs.openstack.org/openstack/i18n-specs.
The git repository is located at http://git.openstack.org/cgit/openstack/i18n-specs/.