BIRCH Stable Release Checklist

From Bioinformatics.Org Wiki

Jump to: navigation, search

Mystica Arrow set (with deep) 1.png [return to BIRCH Project]


Clean out old files, especially from bin directories.

These will typically have a .bak or .old file extension. They usually represent binaries that we might want to keep around for awhile after installing a new version of a program, to make it possible to revert to the old version if necessary.

Review and document recent changes

All changes should be documented in BIRCHDEV/doc/ReleaseNotes.html

Generate a new Development Release, including binaries

Edit BIRCHDEV/build/makeframework.excludefile to exclude all unnecessary files from the $birch/java directory. Mostly these are in the various bioLegato versions. Next, create a development version of the framework file:


Test Development Release on all supported platforms

Generate a Stable Release, but don't list it on the download page.

a. Update the development version of the binaries

makebin.csh solaris-sparc
makebin.csh solaris-amd64
makebin.csh linux-x86_64

Binaries for linux-intel and osx-x86_64 must be generated on the brassica x86 VM and albacore, respectively, and uploaded to the Development directory.

b. Create a new birch framework

makeframework.csh -v  version_number

This script creates a new snapshot called framework_version_number.tar gz. It also copies the tar archives containing the development version of the binaries to new files with the version number. This means that the binary files need to be up to date in the development verison before running makeframework.csh.

c. Add the new version number to birchtally.cgi

Login as birch on flamingo.

cd /usr/lib/cgi-bin/birch

Add the new version number to the list of valid versions in birchtally.cgi.

    Versions = ['D', '3.00','2.96']

birchtally.cgi will fail to record a birch download if its version number is not in the list.

Test on other systems

as in step 3

When satisfied, change the symbolic link CURRENT to point to the new version.


cd /home/psgendb/FTP/BIRCH
ln -s 2.9 CURRENT

In this example, GetBirch will see version 2.9 as the current version for download.


a. Version home page

Edit the BIRCH announcement page at<version>.html

This file is just a copy of the $doc/ReleaseNotes.html. There is still an issue with inline links needing to be changed when the file moves to this directory.

Since it's often good to include hypertext links to new features, we need to install the updated BIRCH version to /home/psgendb, so that the links can point to the new features.

b. BIRCH mailing list

i) Copy /home/psgendb/local/public_html/BIRCHannouncement<version>.html to /home/frist/software/BIRCH/Distribution.

ii> modify as follows:

Email message files are HTML, but begin with Subject: and a blank line For compliance with anti-spam laws in Canada and elsewhere, the message begins with unsubscribe instructions.


Subject: BIRCH 3.10 Bioinformatics System

<table border="1">
<td>To unsubscribe, reply to this message with the word UNSUBSCRIBE in the Subject line.</td>
<h1>BIRCH 3.10</h1>
<i>the rest of the message....</i>

iv) Do a test mailing using

python test.mailinglist.txt BIRCH3.10announcement.html

This script mails htmlfile to the specified mailing list.

v) If the mail message looks good, send it to the actual mailing list:

python mailinglist.txt BIRCH3.10announcement.html

Mailing lists:

Note: It probably makes sense to send out announcements to the mailing lists on list per day. Usually in the first 24 hr. after a mailing, you get a few of Mail Delivery System messages saying that a user is not found. This way, you know which mailinglist to delete an email address from.

Before doing further announcements, give people a week or two to see if there are problems.

vi. Other places to announce:

Personal tools
wiki navigation