Required tools

To build a binary release of OpenMeetings you need:

  • Sun JDK8
  • Apache Maven 3.3.9
  • Git Command line client
  • A text editor
  • You need to be online! The build process actively downloads needed libraries and dependencies.
  • Valid certficate to be able to enter https://securesigning.websecurity.symantec.com/csportal/ Please ask INFRA in case you need one.

Prepare your Apache ID

Step1 - Prepare files

  • Switch to the necessary branch:
    git checkout BRANCH
    						
  • Check that all files:
    LICENSE, NOTICE, DISCLAIMER, CHANGELOG, README
    are up to date and refer to the right version.
  • Update following files in OM documentation:
    openmeetings-server/src/site/xdoc/index.xml
    openmeetings-server/src/site/xdoc/NewsArchive.xml
    openmeetings-server/src/site/xdoc/downloads.xml
  • Create a TAG of the Git tree that you would like to release
    Example:
    git tag 4.0.0RC1
    git push origin 4.0.0RC1
    						
  • Get the source from your TAG:

    git checkout $BRANCHORTAG

    $BRANCHORTAG should be replaced with your new TAG

  • Update versions of all modules

    mvn versions:set -DgenerateBackupPoms=false -DnewVersion=3.1.0
  • Deploy release artifacts to Maven
    • mvn clean
      mvn deploy -Pdeploy,rc
      							
  • Run the command:

    mvn clean install -P allModules,rc
  • Test building the source on windows and OSx or Linux

    Test running the binary's

  • Commit artifacts you have created with KEYS file to the https://dist.apache.org/repos/dist/dev/openmeetings/ Proposed file structure for "Release Candidate 1" of 3.1.0 will be:

    3.1.0
    3.1.0/rc1
    3.1.0/rc1/src
    3.1.0/rc1/src/apache-openmeetings-3.1.0-src.zip
    3.1.0/rc1/src/apache-openmeetings-3.1.0-src.tar.gz
    3.1.0/rc1/src/apache-openmeetings-3.1.0-src.zip.sha
    3.1.0/rc1/src/apache-openmeetings-3.1.0-src.zip.asc
    3.1.0/rc1/src/apache-openmeetings-3.1.0-src.tar.gz.sha
    3.1.0/rc1/src/apache-openmeetings-3.1.0-src.tar.gz.asc
    3.1.0/rc1/bin
    3.1.0/rc1/bin/apache-openmeetings-3.1.0.zip
    3.1.0/rc1/bin/apache-openmeetings-3.1.0.tar.gz
    3.1.0/rc1/bin/apache-openmeetings-3.1.0.zip.sha
    3.1.0/rc1/bin/apache-openmeetings-3.1.0.zip.asc
    3.1.0/rc1/bin/apache-openmeetings-3.1.0.tar.gz.sha
    3.1.0/rc1/bin/apache-openmeetings-3.1.0.tar.gz.asc
    3.1.0/rc1/CHANGELOG
    3.1.0/rc1/KEYS
    						

Step2 - VOTE and RESULT emails

Send a "VOTE" to the developer mailing list including links to release artifacts.
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 example Vote email (Incubator)
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
Votes on whether a package is ready to be released use majority approval -- i.e., at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed. Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases.

Step3 - Sign web start application

If VOTEs positive: Sign screen sharing web application and re-pack the release

  • Go to the folder you check out your $BRANCHORTAG
  • Run the command:

    cd openmeetings-screenshare
    mvn clean install -Prc,release
    						
  • Go to https://securesigning.websecurity.symantec.com/csportal/
  • Select "Signing Sets"
  • Select "Add signing set"
  • Enter "Signing set name" (must include "Apache OpenMeetings" and version) for ex. "Apache OpenMeetings 3.1.0-RELEASE"
  • Enter "Version" for ex. "3.1.0-RELEASE"
  • Select "Java Signing Sha256" as "Signing service"
  • Select "Upload files" and add all jar files from target/jnlp
  • Select "Sign now"
  • Select "Type of signing" -> "Production"
  • Select "Sign"
  • Select "Download set"
  • Open binary artifacts of OM created on previous step (both tar.gz and zip)
  • Replace jar files inside artifacts webapps/openmeetings/screenshare with the signed ones
  • Re-create artifact signatures

    Create sha256sum checksums

    #On OSX you might use this command to make a SHA checksum and store it to a file
    shasum -a 256 -r apache-openmeetings-XXX-src.zip >apache-openmeetings-XXX-src.zip.sha256
    						
    
    #To create SHA hashes On Ubuntu:
    for f in `ls -1 *.tar.gz *.zip`; do sha256sum $f > $f.sha256; done
    
    #To check SHA hashes On Ubuntu:
    for f in `ls -1 *.tar.gz *.zip`; do sha256sum -c $f.sha256; done
    
    						

    Create signatures with the your KEY for every file, the KEY must be available at:
    https://git-wip-us.apache.org/repos/asf/openmeetings.git/KEYS?p=openmeetings.git;a=blob;f=KEYS;hb=HEAD

    
    #To create signatures On Ubuntu:
    for f in `ls -1 *.tar.gz *.zip`; do gpg --armor --output $f.asc --detach-sig $f; done
    
    #To check signatures On Ubuntu:
    for f in `ls -1 *.tar.gz *.zip`; do gpg --verify $f.asc; done
    
    						

NOTE: "Type of signing" can be selected as "Test" to check everything works as expected

Step4 - Distribute and announce

If VOTEs positive: Upload the release

  • Upload Artifacts with signatures created on the previous steps to https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
  • Close staging repo:
    • Go to: Staging Repositories
    • Select openmeetings staging repo and Close it with valid message:
      for ex. "The VOTE about 3.1.2 release was successful"
    • Select openmeetings staging repo and Release it with valid message:
      for ex. "The VOTE about 3.1.2 release was successful"
  • 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 released
  • Update release section of DOAP file openmeetings-site/doap.rdf (https://git-wip-us.apache.org/repos/asf?p=openmeetings-site.git;a=blob;f=doap.rdf;hb=HEAD)
  • Add a section to downloads website.
    Make sure that the binary packages are linked using the mirror URL as base path ( not http://www.apache.org/dist):
    Mirror URL: http://www.apache.org/dyn/closer.lua/openmeetings/
  • Release candidates should be deleted from https://dist.apache.org/repos/dist/dev/openmeetings/
    Old releases should be deleted from https://dist.apache.org/repos/dist/release/openmeetings/

Back to top

Apache OpenMeetings, OpenMeetings, Apache, the Apache feather, and the Apache OpenMeetings project logo

are trademarks of the Apache Software Foundation.