Skip to content

Commit 583c347

Browse files
committed
Remove branch mentions
1 parent 184f604 commit 583c347

File tree

1 file changed

+3
-17
lines changed

1 file changed

+3
-17
lines changed

RELEASING.txt

+3-17
Original file line numberDiff line numberDiff line change
@@ -14,16 +14,8 @@ Releasing
1414
- A *minor* or *bug fix* release is where the number after the second dot
1515
increases. Example: 1.0 to 1.0.1.
1616

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+
-------------------
2719

2820
- Do platform test via tox:
2921

@@ -41,9 +33,6 @@ Prepare new release branch
4133
- Minor releases should include a link under "Bug Fix Releases" to the minor
4234
feature changes in CHANGES.txt.
4335

44-
- Update README.rst to use correct versions of badges, URLs, and ALT option
45-
according to the new release branch name.
46-
4736
- Change setup.py version to the release version number.
4837

4938
- Make sure PyPI long description renders (requires ``readme_renderer``
@@ -63,13 +52,10 @@ Prepare new release branch
6352
Prepare master for further development (major releases only)
6453
------------------------------------------------------------
6554

66-
- Checkout master.
67-
6855
- In CHANGES.txt, preserve headings but clear out content. Add heading
6956
"unreleased" for the version number.
7057

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.
7359

7460
- Change setup.py version to the next version number.
7561

0 commit comments

Comments
 (0)