Required tools

To build a binary release of OpenMeetings you need: Sun JDK6 Apache ANT (minimum) 1.8.3 SVN Command line client (Subversion 1.7 required!) http://subversion.apache.org/packages.html A text editor You need to be online! The build process actively downloads needed libraries and dependencies.

Prepare your Apache ID

Every release package must be signed with a PGP/GPG key. So if you want to release a package your Apache Id must be connected with a PGP key! You might follow: http://www.apache.org/dev/new-committers-guide.html#security-and-pgp In short: Create PGP key pairs (private + public) (and I recommend creating a Revoke Cert) Upload the public key (either bei using the PGP Tool that you use to create the key) or by using the web form to: http://pgp.mit.edu/ Add the fingerprint string (something like "BF13 CF11 F9C9 0CBE 4413 09AB 0055 16BF 93A3 0395") to your profile at id.apche-org Wait for 6-8 hours, the server will search for a public key based on your fingerprint, if success it will create a file with your name at: https://people.apache.org/keys/committer/ If that is "success" then add your key to: https://svn.apache.org/repos/asf/openmeetings/project/KEYS and follow the instructions in the file.

Step1 - Prepare files

Check that all files: LICENSE, NOTICE, DISCLAIMER, CHANGELOG, README are up to date and refer to the right version. Create a TAG of the SVN tree that you would like to release Get the source from your TAG: svn checkout https://svn.apache.org/repos/asf/openmeetings/$TREE/$BRANCHORTAG/ $TREE and $BRANCHORTAG should be replaced with your new TAG Edit the file build.properties project.status=SNAPSHOT to project.status=RELEASE Run the command: ant dist-release Test building the source on windows and OSx or Linux Test running the binary's Create MD5 checksums #On OSX you might use this command to make a MD5 checksum and store it to a file md5 -r apache-openmeetings-XXX-src.zip > apache-openmeetings-XXX-src.zip.md5 Create signatures with the your KEY for every file, the KEY must be available at: http://www.apache.org/dist/incubator/openmeetings/KEYS Upload the build artefacts to your public_html in your home directory at people.apache.org #On OSX you might use this command to upload the file scp apache-openmeetings-XXXX.zip sebawagner@people.apache.org:~/public_html/

Step2 - VOTE and RESULT emails

Send a "VOTE" to the developer mailing list including links to release artefacts. A VOTE always contains two parts: Send an email to the developer mailing list with the subject line: [VOTE] Apache OpenMeetings x.xx release An example for such an email: example Vote email Forward (Not CC) this Vote email to: private@incubator.apache.org After the vote is over, send a "RESULT" email to the list with the subject line: [RESULT][VOTE] Apache OpenMeetings x.xx release An example for such an email: example Result email Forward (Not CC) this RESULT VOTE email to: private@incubator.apache.org After the Vote was successful on the Developer mailing list, you need organize a vote on the general list: general@incubator.apache.org The vote on the general list has the same process, first a VOTE email, then a RESULT email. You need at least 3 IPMC votes for the release. You can summarize the IPMC votes from both votes (dev + general).

Step3 - Distribute and announce

If VOTEs positive: Upload the release The distribution upload location (www.apache.org/dist) for all Apache projects is the /www/www.apache.org/dist directory on people.apache.org. Each project owns a directory within dist. Our distribution directory is: /www/www.apache.org/dist/incubator/openmeetings each version should have a subfolder within this directory matching the name of the release: for example 2.0 Make sure the the files/folders in the section /www/www.apache.org/dist/incubator/openmeetings have the proper rights, see: http://incubator.apache.org/guides/releasemanagement.html#distribution-permissions Wait 24 hours (until all Apache mirrors have synced the packages) and send an announcement to the mailing list + blog and any other channel. Email announcements should have the subject line: [ANNOUNCE] Apache OpenMeetings x.xx [Incubating] released Add a section to downloads website. Make sure that the binary packages are linked using the mirror URL as base path ( not www.apache.org/dist): Mirror URL: http://www.apache.org/dyn/closer.cgi/incubator/openmeetings/