-
-
Notifications
You must be signed in to change notification settings - Fork 80
how to make a release
I'm absent-minded and use this for making general a release, posting announcements, and updating site documentation. It's possible there's information for other purposes such as for packages. However your milage may vary.
Update NEWS.remake REMAKE_VERSION=1.2
- Change configure.ac release name. E.g.
define(_MAKE_VERSION_, 4.3)
^^^^ Possibly this
AC_INIT([remake],[_MAKE_VERSION_+dbg-1.6],[https://github.com/rocky/remake/issues])
^^^ and this
export REMAKE_VERSION="4.3+dbg-1.6"
-
Let people know of a pending release, e.g. [email protected]; no major changes before release, please
-
test on lots of platforms; panix, login.opencsw, cygwin
-
Go over
Changelogand addNEWS-remake.md. Update date of release. -
Make sure sources are current and checked in: git pull git commit -m"Get ready for release $REMAKE_VERSION" . git push
-
make distcheckshould work For now, remove `.o's afterwards' -
recreate the documentation so we can put it on the public website: (In theory be could/should be done after the release but if there's a problem we want to know about it beforehand)
cd doc remake remake.html remake.dvi
-
Add release to github https://github.com/rocky/remake/releases/new git tag release-remake-$REMAKE_VERSION git push --tags
-
"make distcheck" one more time
-
Get onto sourceforge: Use the GUI login, develop, Project Amin, File Manager
-
copy remake and remake manual to web page: cd ../remake/doc && make remake.html ??? sftp -i ~/.ssh/id_rsa_sourceforge rockyb,[email protected] also works cd htdocs/remake put -R remake.html
-
Bump version in configure.ac and add "dev". See place above in removal.