Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitfee2444

Browse files
authored
Merge pull request#1707 from EliahKagan/no-milestones
Update readme for milestone-less releasing
2 parents10e2960 +feb4414 commitfee2444

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

‎README.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -198,15 +198,13 @@ Please have a look at the [contributions file][contributing].
198198

199199
###How to make a new release
200200

201-
- Update/verify the**version** in the`VERSION` file.
202-
- Update/verify that the`doc/source/changes.rst` changelog file was updated.
203-
- Commit everything.
204-
- Run`git tag -s <version>` to tag the version in Git.
205-
-_Optionally_ create and activate a[virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment) using`venv` or`virtualenv`.\
206-
(When run in a virtual environment, the next step will automatically take care of installing`build` and`twine` in it.)
207-
- Run`make release`.
208-
- Close the milestone mentioned in the_changelog_ and create a new one._Do not reuse milestones by renaming them_.
209-
- Go to[GitHub Releases](https://github.com/gitpython-developers/GitPython/releases) and publish a new one with the recently pushed tag. Generate the changelog.
201+
1. Update/verify the**version** in the`VERSION` file.
202+
2. Update/verify that the`doc/source/changes.rst` changelog file was updated. It should include a link to the forthcoming release page:`https://github.com/gitpython-developers/GitPython/releases/tag/<version>`
203+
3. Commit everything.
204+
4. Run`git tag -s <version>` to tag the version in Git.
205+
5._Optionally_ create and activate a[virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment). (Then the next step can install`build` and`twine`.)
206+
6. Run`make release`.
207+
7. Go to[GitHub Releases](https://github.com/gitpython-developers/GitPython/releases) and publish a new one with the recently pushed tag. Generate the changelog.
210208

211209
###How to verify a release (DEPRECATED)
212210

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp