Tuleap release process

Note

This section describes release processes of Tuleap and is only relevant for contributors endorsing the role of release manager.

A release manager needs to:

Release a new Tuleap stable milestone

A new Tuleap stable milestone can be released once:
  • the set of features included in the release has been validated by the Product Owner
  • full validation test suite has been passed with success (all major spotted bugs has been fixed)
  • no Tuleap integrator has manifested himself with a reason to block the release

Prepare the source repositories for the release

The source repositories must be prepared to release a new Tuleap stable milestone. The release manager must sign with his GPG key any commits or any tags created during the release process.

This document consider that X.Y is the version number of Tuleap that you want to release.

Tuleap

You should retrieve the sources of the master branch of the stable repositories. You will also need a remote to the Gerrit repository. The top of the master branch must be what you want to release. Your workspace copy must be up to date and at the top of the master branch.

  1. Verify that all VERSION files of the plugins and themes has been correctly updated:

    $ php ./tools/rpm/check_release/check_release_git.php
    
  2. Update /VERSION to the X.Y version you are releasing

  3. Commit:

    $ git commit -S -a -m 'This is Tuleap X.Y'
    
  4. Tag:

    $ git tag -s -m 'Create tag for Tuleap X.Y' X.Y
    
  5. Publish your commit and tag:

    $ git push stable HEAD:master
    $ git push gerrit HEAD:master
    $ git push stable X.Y
    

Documentation

Both the English documentation and French documentation must be updated, so you need to clone both repositories.

1. Verify that the deployment guide in the english documentation is up to date. You can partially achieve that by checking if there was changes in the configuration files:

$ git diff X.W..X.Y -- plugins/*/etc/ src/etc
  1. Create a branch specific to the release in the English and French documentation repositories:

    $ git checkout -b X.Y origin/master
    
  2. Edit, if needed, the copyright, version and release:

    # In English documentation repository
    $ vim languages/en/conf.py
    # In French documentation repository
    $ vim languages/fr/conf.py
    
  3. Edit, if needed, the deployment guide to remove the mention “Under development”

  4. Commit your changes and publish them:

    # In English documentation repository
    $ git commit -S -a -m 'Initialize documentation for Tuleap X.Y'
    # In French documentation repository
    $ git commit -S -a -m 'Initialisation de la documentation de Tuleap X.Y'
    # In both repositories
    $ git push -u origin HEAD
    

Plugins and tools external to the main Tuleap repository

Some plugins and tools are not in the main Tuleap repository as such their versions must be updated and tagged individually.

The list of the concerned plugins and tools can be found in the manifest file.

The procedure to follow is similar for each one of the concerned plugins and tools:
  1. Clone the repository or update your local workspace to be on the top of the remote master branch

2. Verify if changes has been made since the last Tuleap stable milestone release. If the top of the master branch is the tag created for the last release you can stop, else you need to continue the procedure.

3. Edit /VERSION file with the new version number. These repositories follow SemVer, so you need to either increment MAJOR or MINOR version and reset the PATCH version to 0. The rest of this procedure assumes that you are releasing the version T.U.0 of the plugin or tool:

$ echo 'T.U.0' > VERSION
  1. Commit:

    $ git commit -S -a -m 'Version T.U.0'
    
  2. Tag:

    $ git tag -s -m 'Version T.U.0' T.U.0
    
  3. Publish your commit and tag:

    $ git push --follow-tags
    

Update the manifest

What goes into a Tuleap stable milestone is defined by a manifest file.

  1. Clone or update your local copy of the release-manisfest repository

  2. Edit the release manifest file located in stable/manifest.json with the tags you have created for the release

  3. Commit the new manifest and publish it:

    $ git commit -S -a -m 'Release Tuleap stable X.Y'
    $ git push
    

Build and publish packages

Building and publishing the packages is fully automated through a Jenkins pipeline. The only thing you need to do is to start it once you’re ready.

You should wait for the pipeline to complete before finishing the release process.

Update Tuleap.net

Release or update a dependency delivered in the Tuleap RPM repository

This action is only needed when it is needed to publish a dependency package that is not built in the standard build pipeline of Tuleap. This is something that is rarely needed. Ensure you really need it before going further.

Note

Publishing a RPM package manually in the RPM repository is only accessible to Tuleap integrators with:

  • a SSH access to ci.tuleap.org
  • an account on the Hashicorp Vault managed by Enalean with the permission to access to the GPG key used to sign packages
  1. Build the package you want to publish
  2. Sign the package with the script helpers/sign-packages.sh provided in the Git repository sign-packages-repositories
  3. Upload the signed package to ci.tuleap.org in /var/lib/jenkins/pub/tuleap/upstream/rhel/VERSION/PHPBASE where:
    • VERSION is the major release of the OS (either 6 or 7)
    • PHPBASE either common for RHEL6 or noarch for RHEL7
  4. The package will be published with the next automated build of Tuleap