We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent c2636d2 commit 7493057Copy full SHA for 7493057
README.md
@@ -110,12 +110,13 @@ Please have a look at the [contributions file][contributing].
110
111
### How to make a new release
112
113
-* Update/verify the version in the `VERSION` file
114
-* Update/verify that the changelog has been updated
+* Update/verify the **version** in the `VERSION` file
+* Update/verify that the `doc/source/changes.rst`changelog file was updated
115
* Commit everything
116
* Run `git tag -s <version>` to tag the version in Git
117
* Run `make release`
118
-* Finally, set the upcoming version in the `VERSION` file, usually be
+* Close the milestone mentioned in the _changelog_ and create a new one. _Do not reuse milestones by renaming them_.
119
+* set the upcoming version in the `VERSION` file, usually be
120
incrementing the patch level, and possibly by appending `-dev`. Probably you
121
want to `git push` once more.
122
doc/source/changes.rst
@@ -2,6 +2,12 @@
2
Changelog
3
=========
4
5
+3.0.4 - Bugfixes
6
+=============================================
7
+
8
+see the following for details:
9
+https://github.com/gitpython-developers/gitpython/milestone/31?closed=1
10
11
3.0.3 - Bugfixes
12
=============================================
13
AltStyle によって変換されたページ (->オリジナル) / アドレス: モード: デフォルト 音声ブラウザ ルビ付き 配色反転 文字拡大 モバイル
0 commit comments