diff options
author | Daiki Ueno <ueno@gnu.org> | 2020-06-07 15:46:51 +0200 |
---|---|---|
committer | Daiki Ueno <ueno@gnu.org> | 2020-06-07 15:48:42 +0200 |
commit | 7b75424f28bd1ed1e4cca613e182d09b7eab4009 (patch) | |
tree | c6e7b845759d60262f634de07bf72c33ef421c21 | |
parent | d285844ffd7c134048e58a34f5199add841f072b (diff) | |
download | gnutls-tmp-doc-fixes.tar.gz |
RELEASES.md: move the release steps to devel/ [ci skip]tmp-doc-fixes
As the information is only useful to developers, having it under
devel/ rather than in the tarball is more releavant.
Signed-off-by: Daiki Ueno <ueno@gnu.org>
-rw-r--r-- | RELEASES.md | 26 | ||||
-rw-r--r-- | devel/release-steps.md | 24 |
2 files changed, 24 insertions, 26 deletions
diff --git a/RELEASES.md b/RELEASES.md index f6aca843fe..53360df3d6 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -16,29 +16,3 @@ cases change the API. |:----:|:-----:|:--------------:| |stable|3.6.x |as needed | |next |3.7.x |bi-monthly | - - -# Release process - - 0. Create a new 'milestone' for the next release and move all issues present in the - current release milestone. - 1. Verification of release notes: ensure that release notes ([NEWS](NEWS)) exist - for this release, and include all significant changes since last release. - 2. Update of release date in [NEWS](NEWS), and bump of version number in - [configure.ac](configure.ac) as well as soname numbers in [m4/hooks.m4](m4/hooks.m4). - 3. make distcheck - 4. git tag -s $(VERSION). The 3.6.12 was including both the 3.6.12 and - gnutls_3_6_12 tags, but it may make sense to only use the version from - now on. - 5. git push && git push --tags - 6. make dist && gpg --sign --detach gnutls-$(VERSION).tar.xz - 7. scp gnutls-$(VERSION).tar.xz* ftp.gnupg.org:/home/ftp/gcrypt/gnutls/v3.6/ - 8. Create and send announcement email based on previously sent email to the list and - [NEWS](NEWS) file. - 9. Create a NEWS entry at [web-pages repository](https://gitlab.com/gnutls/web-pages/-/tree/master/news-entries), - and/or [a security advisory entry](https://gitlab.com/gnutls/web-pages/-/tree/master/security-entries) - if necessary. The NEWS entry is usually pointing to the announcement email. - A commit auto-generates the [gnutls web site](https://gnutls.gitlab.io/web-pages/) - which is mirrored twice a day by www.gnutls.org. -10. Use the @GnuTLS twitter account to announce the release. -11. Close the current release milestone. diff --git a/devel/release-steps.md b/devel/release-steps.md new file mode 100644 index 0000000000..04e7b2dfa5 --- /dev/null +++ b/devel/release-steps.md @@ -0,0 +1,24 @@ +# Release process + + 0. Create a new 'milestone' for the next release and move all issues present in the + current release milestone. + 1. Verification of release notes: ensure that release notes ([NEWS](NEWS)) exist + for this release, and include all significant changes since last release. + 2. Update of release date in [NEWS](NEWS), and bump of version number in + [configure.ac](configure.ac) as well as soname numbers in [m4/hooks.m4](m4/hooks.m4). + 3. make distcheck + 4. git tag -s $(VERSION). The 3.6.12 was including both the 3.6.12 and + gnutls_3_6_12 tags, but it may make sense to only use the version from + now on. + 5. git push && git push --tags + 6. make dist && gpg --sign --detach gnutls-$(VERSION).tar.xz + 7. scp gnutls-$(VERSION).tar.xz* ftp.gnupg.org:/home/ftp/gcrypt/gnutls/v3.6/ + 8. Create and send announcement email based on previously sent email to the list and + [NEWS](NEWS) file. + 9. Create a NEWS entry at [web-pages repository](https://gitlab.com/gnutls/web-pages/-/tree/master/news-entries), + and/or [a security advisory entry](https://gitlab.com/gnutls/web-pages/-/tree/master/security-entries) + if necessary. The NEWS entry is usually pointing to the announcement email. + A commit auto-generates the [gnutls web site](https://gnutls.gitlab.io/web-pages/) + which is mirrored twice a day by www.gnutls.org. +10. Use the @GnuTLS twitter account to announce the release. +11. Close the current release milestone. |