HOWTO-RELEASE: update online docs *after* uploading release
It doesn't make sense to have docs online relating to a release which isn't yet available; it's less confusing to have a small time window in which the online docs are out of date.
This commit is contained in:
parent
9f59494d4e
commit
cfb3ff7eff
1 changed files with 6 additions and 6 deletions
|
@ -86,6 +86,12 @@ Release procedure
|
|||
git push github
|
||||
git push --tags github
|
||||
|
||||
- Upload the new release to ftp.gnu.org. This is easiest using gnupload:
|
||||
|
||||
- git clone git://git.savannah.gnu.org/gnulib.git
|
||||
- Copy gnulib/build-aux/gnupload to somewhere on your $PATH
|
||||
- Run gnupload --to ftp.gnu.org:stow --symlink-regex stow-7.8.9.tar.*
|
||||
|
||||
- Regenerate the documentation for the website:
|
||||
|
||||
# First check out gnulib repository via:
|
||||
|
@ -113,12 +119,6 @@ Release procedure
|
|||
# Then commit
|
||||
cvs commit -m "Update manual to v$version"
|
||||
|
||||
- Upload to ftp.gnu.org. This is easiest using gnupload:
|
||||
|
||||
- git clone git://git.savannah.gnu.org/gnulib.git
|
||||
- Copy gnulib/build-aux/gnupload to somewhere on your $PATH
|
||||
- Run gnupload --to ftp.gnu.org:stow --symlink-regex stow-7.8.9.tar.*
|
||||
|
||||
- Send release announcements to
|
||||
|
||||
- info-stow@gnu.org
|
||||
|
|
Loading…
Reference in a new issue