diff options
| author | Anil Khatri <27620628+imkaka@users.noreply.github.com> | 2019-10-23 23:37:43 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-23 23:37:43 +0530 |
| commit | abb18968516c6c3c9e1d736bfe6f435392b3d3af (patch) | |
| tree | 46b45bc52901f0f52526f9573f06b2fc0f777231 /README.md | |
| parent | 284f89d768080cb86e0d986bfa1dd503cfe6b682 (diff) | |
| parent | dfa0eac1578bff14a8f7fa00bfc3c57aba24f877 (diff) | |
| download | GitPython-abb18968516c6c3c9e1d736bfe6f435392b3d3af.tar.gz GitPython-abb18968516c6c3c9e1d736bfe6f435392b3d3af.zip | |
Merge branch 'master' into fix/deepsource-issues
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -110,12 +110,13 @@ Please have a look at the [contributions file][contributing]. ### How to make a new release -* Update/verify the version in the `VERSION` file -* 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 * Commit everything * Run `git tag -s <version>` to tag the version in Git * Run `make release` -* 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_. +* set the upcoming version in the `VERSION` file, usually be incrementing the patch level, and possibly by appending `-dev`. Probably you want to `git push` once more. |