| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -110,12 +110,13 @@ Please have a look at the [contributions file][contributing]. | |||
| 110 | 110 | ||
| 111 | 111 | ### How to make a new release | |
| 112 | 112 | ||
| 113 | - * Update/verify the version in the `VERSION` file | ||
| 114 | - * Update/verify that the changelog has been updated | ||
| 113 | + * Update/verify the **version** in the `VERSION` file | ||
| 114 | + * Update/verify that the `doc/source/changes.rst` changelog file was updated | ||
| 115 | 115 | * Commit everything | |
| 116 | 116 | * Run `git tag -s <version>` to tag the version in Git | |
| 117 | 117 | * Run `make release` | |
| 118 | - * Finally, set the upcoming version in the `VERSION` file, usually be | ||
| 118 | + * 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 | ||
| 119 | 120 | incrementing the patch level, and possibly by appending `-dev`. Probably you | |
| 120 | 121 | want to `git push` once more. | |
| 121 | 122 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -2,6 +2,12 @@ | |||
| 2 | 2 | Changelog | |
| 3 | 3 | ========= | |
| 4 | 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 | + | ||
| 5 | 11 | 3.0.3 - Bugfixes | |
| 6 | 12 | ============================================= | |
| 7 | 13 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments