-
Notifications
You must be signed in to change notification settings - Fork 791
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4162 from rouault/howto_release_zenodo
HOWTO-RELEASE: add a step to check GitHub Zeonodo integration
- Loading branch information
Showing
1 changed file
with
8 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -174,15 +174,21 @@ git tag -a -m "Create tag x.y.z" x.y.z | |
git push --tags | ||
``` | ||
|
||
### 2.4 Prepare the release on GitHub | ||
### 2.4 Check the GitHub Zeonodo integration | ||
|
||
Go to https://zenodo.org/account/settings/github/ and check that the OSGeo/PROJ | ||
repository is ON so that the creation of the GitHub release triggers the | ||
creation of a corresponding Zenodo record. | ||
|
||
### 2.5 Prepare the release on GitHub | ||
|
||
When the new tag is pushed upstream GitHub picks up that a new release has been | ||
issued. Update the new release on <https://github.com/OSGeo/PROJ/releases> with | ||
the release notes from `NEWS.md` and add the prepared source distribution archives | ||
to the release (otherwise GitHub will just package the entire repository - we | ||
don't want that). | ||
|
||
### 2.5 Announce the new release | ||
### 2.6 Announce the new release | ||
|
||
The release should be announced on PROJ and MetaCRS mailing lists. Additionally | ||
the release announcement should be sent to <[email protected]> which will add | ||
|