- Notifications
You must be signed in to change notification settings - Fork 12
Release procedure
This page has a detailed step-by-step instructions for a developer to follow to release a new version of the DtdAnalyzer package.
Make sure the README.md is up-to-date with any important changes. (Don't worry about the version numbers.)
Make sure that
ReleaseNotes.md
has all the new features, enhancements, etc.Decide on version number, e.g.,
0.8
(for something fairly major) or0.8.12
(for mostly bug-fixes) and then runscript/fixversion.pl <version>
Commit and push.
[Optional, if you think there might be a lot of cruft in your working directory.] Move your working repository out of the way, and clone a fresh writable copy of the repository; for example,
$ mv DtdAnalyzer DtdAnalyzer.save $ git clone git@github.com:ncbi/DtdAnalyzer.git
Do a full build, with the command
ant
. Make sure this builds the zip files. Check the size of the zip files to make sure they are sane (~5 Meg).Run
script/push-website.pl
Try it out from the zip files, downloaded from the buttons in the DtdAnalyzer home pages.
If that works, then push the website to production.
Tag the repository with the new version number (“
v0.8
”), and push that tag:
``` $ git tag -a v0.8 -m 'Tagging version 0.8' $ git push --tags ```
Run
script/fixversion.pl dev
to set append "-dev" to the version number.Commit and push that, one last time.
Announce to (ideas): * JATS list * xml-dev list * Google plus * Twitter