Skip to content

Commit

Permalink
Remove branch mentions
Browse files Browse the repository at this point in the history
  • Loading branch information
stevepiercy committed May 20, 2018
1 parent 184f604 commit 583c347
Showing 1 changed file with 3 additions and 17 deletions.
20 changes: 3 additions & 17 deletions RELEASING.txt
Original file line number Diff line number Diff line change
Expand Up @@ -14,16 +14,8 @@ Releasing
- A *minor* or *bug fix* release is where the number after the second dot
increases. Example: 1.0 to 1.0.1.

Prepare new release branch
--------------------------

- Create a new release branch, incrementing the version number.

- Do any necessary branch merges (e.g., master to branch, branch to master).

- On release branch:

$ git pull
Prepare new release
-------------------

- Do platform test via tox:

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

- Update README.rst to use correct versions of badges, URLs, and ALT option
according to the new release branch name.

- Change setup.py version to the release version number.

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

- Checkout master.

- In CHANGES.txt, preserve headings but clear out content. Add heading
"unreleased" for the version number.

- From the release branch, forward port the changes in CHANGES.txt to
HISTORY.txt.
- Forward port the changes in CHANGES.txt to HISTORY.txt.

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

Expand Down

0 comments on commit 583c347

Please sign in to comment.