@@ -14,16 +14,8 @@ Releasing
14
14
- A *minor* or *bug fix* release is where the number after the second dot
15
15
increases. Example: 1.0 to 1.0.1.
16
16
17
- Prepare new release branch
18
- --------------------------
19
-
20
- - Create a new release branch, incrementing the version number.
21
-
22
- - Do any necessary branch merges (e.g., master to branch, branch to master).
23
-
24
- - On release branch:
25
-
26
- $ git pull
17
+ Prepare new release
18
+ -------------------
27
19
28
20
- Do platform test via tox:
29
21
@@ -41,9 +33,6 @@ Prepare new release branch
41
33
- Minor releases should include a link under "Bug Fix Releases" to the minor
42
34
feature changes in CHANGES.txt.
43
35
44
- - Update README.rst to use correct versions of badges, URLs, and ALT option
45
- according to the new release branch name.
46
-
47
36
- Change setup.py version to the release version number.
48
37
49
38
- Make sure PyPI long description renders (requires ``readme_renderer``
@@ -63,13 +52,10 @@ Prepare new release branch
63
52
Prepare master for further development (major releases only)
64
53
------------------------------------------------------------
65
54
66
- - Checkout master.
67
-
68
55
- In CHANGES.txt, preserve headings but clear out content. Add heading
69
56
"unreleased" for the version number.
70
57
71
- - From the release branch, forward port the changes in CHANGES.txt to
72
- HISTORY.txt.
58
+ - Forward port the changes in CHANGES.txt to HISTORY.txt.
73
59
74
60
- Change setup.py version to the next version number.
75
61
0 commit comments