Difference between revisions of "Blueprint-version-py"
m (Text replace - "__NOTOC__" to "") |
m (Fungi moved page +1 (888) 990-8801 Thunderbird™ Support Number to Blueprint-version-py without leaving a redirect: revert) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | * '''Launchpad Entry''': | + | * '''Launchpad Entry''': NovaSpec:version-py |
* '''Created''': | * '''Created''': | ||
* '''Contributors''': | * '''Contributors''': |
Latest revision as of 16:26, 25 August 2016
- Launchpad Entry: NovaSpec:version-py
- Created:
- Contributors:
Summary
Provide a programmatic way to interact with the version of nova.
Release Note
Include version.py that exposes version information.
Rationale
We can build a file that stores version information in a single place. That information can be used for logging, documentation, and checking compatibility by third-party libraries. The file can be updated when setup.py is run to include branch information from bzr.
Design
This is based on guidance from Soren, who has done this sort of thing before.
Implementation
Check lp:~anso/nova/deploy. Still needs to interact with doc/source/conf.py, though.