-
Notifications
You must be signed in to change notification settings - Fork 103
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
RELEASE-PROCEDURE: how to do a trurl release
Maybe with a checklist we can avoid repeating some mistakes...
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 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 |
---|---|---|
@@ -0,0 +1,24 @@ | ||
trurl release procedure - how to do a release | ||
============================================== | ||
|
||
in the source code repo | ||
----------------------- | ||
|
||
- edit `RELEASE-NOTES` to be accurate | ||
|
||
- edit `version.h` to contain the correct version | ||
|
||
- make sure all relevant changes are committed on the master branch | ||
|
||
- tag the git repo in this style: `git tag -a trurl-[version]` -a annotates | ||
the tag | ||
|
||
- push the git commits and the new tag | ||
|
||
- Go to https://github.com/curl/trurl/tags and edit the tag as a release | ||
Consider allowing it to make a discussion post about it. | ||
|
||
celebrate | ||
--------- | ||
|
||
- suitable beverage intake is encouraged for the festivities |