-
Notifications
You must be signed in to change notification settings - Fork 27
Mesquite Package Release Protocol
David Maddison edited this page Apr 10, 2023
·
31 revisions
- update version numbers and dates, including on banner and on home page. (Current Version, template, required version of Mesquite, etc.)
- update citation page
- update links on download page (if needed)
- update page showing release dates (if needed)
- update notices.xml and install.xml if in docs folder
- set build number, version number, release dates, prerelease flag in aPackageIntro subclass. Also change values in the two getMinimumMesquiteVersionRequired methods.
- check prerelease modules (use Help>List of prerelease modules): check code and switch those deemed safe to isPrerelease = false;
- search code for Debugg. (should be no instances in release)
- (no longer needed?) check that no class files are old (this is symptom of remnants or something not getting compiled); may not be needed with new system
- for new modules modify getVersionOfFirstRelease, returning negative integer value of package version; replace constant NEXTRELEASE if that had been used.
- make sure updates.xml, notices.xml, install.xml are updated. For download URL, make sure that the tag and file name are correct (the URL should end in /[tag]/[zip file name]
- Make sure docs folder is in package folder in Mesquite_Folder/package, not just in Source
- push final changes, including new updates.xml and notices.xml, to GitHub
- copy package directory and remove .DS_Store files using find . -name ".*" -exec rm -rf {} \;
- .zip cleaned directory using NOT the standard MacOS X Compress File feature, but instead something like YemuZip that removes the extraneous files etc. made by the Mac. (If you use YemuZip, as to save the zip file with the "PC" option.)
- also tar produce .tgz file, e.g.:
- tar -czf zephyr.3.30.tgz zephyr
- tar -czf chromaseq.1.60.tgz chromaseq
- tar -czf cartographer.1.60.tgz cartographer
- if the development fork is not the master, then go to the main repository and create a pull request (it should have the master as the base fork)
- do formal release. Use the form "v3.01" for the tag (and make sure this matches the tag embedded in the download URL in the installing and updating XML files).
- update notices.xml and install.xml if they are housed on a server other than GitHub
- if needed, update manual pages in mesquiteproject.org/packages/ or elsewhere