Release 1.1.0 and use pbr 0.11 features.
This commit is contained in:
parent
89856bda75
commit
18ea57d2ef
6
HACKING
6
HACKING
|
@ -36,12 +36,12 @@ the fixtures __init__.py.
|
|||
Releasing
|
||||
+++++++++
|
||||
|
||||
1. Update the version number in __init__.py and add a version to NEWS.
|
||||
|
||||
1. Upload to pypi, signed.
|
||||
1. Add a version to NEWS.
|
||||
|
||||
1. commit, tag.
|
||||
|
||||
1. Upload to pypi, signed.
|
||||
|
||||
1. Close bugs.
|
||||
|
||||
1. Rename the next milestone, release it, and make a new one.
|
||||
|
|
|
@ -36,13 +36,10 @@ Most users will want to look at TestWithFixtures and Fixture, to start with.
|
|||
# established at this point, and setup.py will use a version of next-$(revno).
|
||||
# If the releaselevel is 'final', then the tarball will be major.minor.micro.
|
||||
# Otherwise it is major.minor.micro~$(revno).
|
||||
|
||||
# Uncomment when pbr 0.11 is released.
|
||||
#import pbr.version
|
||||
#_version = pbr.version.VersionInfo('fixtures').semantic_version()
|
||||
#__version__ = _version.version_tuple()
|
||||
#version = _version.release_string()
|
||||
__version__ = (1, 0, 0, 'final', 0)
|
||||
from pbr.version import VersionInfo
|
||||
_version = VersionInfo('fixtures')
|
||||
__version__ = _version.semantic_version().version_tuple()
|
||||
version = _version.release_string()
|
||||
|
||||
|
||||
__all__ = [
|
||||
|
|
|
@ -1 +1,2 @@
|
|||
pbr>=0.11
|
||||
testtools>=0.9.22
|
||||
|
|
Loading…
Reference in New Issue