Home

Mesquite Release Protocol

##Code

add new features/bug fixes to History of New Features page (check Help>List of new modules)
(major only) examine and possibly resave example files
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)
(major only) test under Windows, Linux, OSX 10.4
(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 return current release for getVersionOfFirstRelease; replace constant NEXTRELEASE if that had been used.
set build numbers and version numbers in MesquiteModule.java
set release dates, version, version numbers, prerelease in Mesquite.java
(major only) headless recompile

##Wiki

update module list in wiki. You can output a list of all modules installed using items in the Help menu. Paste into a Textwrangler file; sort and do same for previous version. Do a file comparison to discover new modules. If any add them to the module list in the manual. (You can also build module list from scratch by searching and replacing & for & then \t for — then
into the list and pasting into the source view of the module list html page.) You may find it useful to output class file names of modules instead (in case names have changed); send command dumpAllModuleClasses to Mesquite
check version number and released dates in wiki
convert wiki to PDF and upload to mesquiteproject.org

##Server files

(major only) add new mesquiteFeedbackXXX.py and adjust accordingly, move to server, and set EXECUTABLE bits
change update.xml URL in Installer and Defaults to real ones if needed

##GitHub