Release Process

Prerequisite

Note: Send notification in the Slack eclipse-dirigible workspace, that release is going to be scheduled.

@channel Hi team,

Release X.Y.Z is being scheduled for today.
Please let us know, if there are any pending changes, that needs to be included in this release. 

Regards,
XXX

Pre-release

Triggering the Pre-release action is useful for test & development purposes.

Note: The output artefacts (Docker images, Buildpacks and Helm charts) will be overridden by the Release action. No other release artefacts are published (*.jar, *.war, Release Notes, etc.).

1. Pull the latest changes:

   git pull
   

2. Trigger the GitHub Pre-release action:

   git tag pre6.2.0
   git push origin pre6.2.0
   

3. Wait for the release action to complete.

   Usually it takes around 30 minutes! To check the pre-release action progress, go here.

4. Drop the pre-release tag

   git tag -d pre6.2.0
   git push --delete origin pre6.2.0
   

Release

1. Check the Build GitHub action status.

2. Pull the latest changes:

   git pull
   

3. Set the release version:

   mvn versions:set -DnewVersion=6.2.0
   git add .
   git commit -m "version set to 6.2.0 for release"
   git push
   

4. Trigger the GitHub Release action:

   git tag v6.2.0
   git push origin v6.2.0
   

   Note: Check https://status.maven.org/ before triggering the release!

   There could be a maintenance going on during the build, if that's the case, usually the Publish packages to Maven Central step will fail with 405 Not Allowed.

5. Wait for the release action to complete.

   Usually it takes around 1 hour! To check the release action progress, go here.

6. Check the latest release:

   Go to: https://github.com/eclipse/dirigible/releases

7. Check if a release branch was created from here.

   If there is no release branch created automatically, create one manually - e.g. 5.4.0

8. Close and Release the uploaded content to Maven Central:

   Login to: https://oss.sonatype.org/#stagingRepositories

   • Close
   • Release

9. Validate Trial:

   Go to: http://trial.dirigible.io and check the version from the About view.

10. Set the development version:

    mvn versions:set -DnewVersion=7.0.0-SNAPSHOT
    git add .
    git commit -m "version set to 7.0.0-SNAPSHOT for development"
    git push
    

Post Release Actions

Note: Send notification in the Slack eclipse-dirigible workspace, that release is published

@channel Hi Team,

Release X.Y.Z is published now: http://download.dirigible.io/

Regards,
XXX

Advertising

1. Create the Release Notes:

   Go to: https://github.com/dirigible-io/dirigible-io.github.io/tree/master/_posts/releases

2. Notify community via e-mail

   Send e-mail to [email protected] by template:

   Release: <release version, e.g. 6.2.0>

   Hi All,
   
   The major/minor/micro version <release version, e.g. 6.2.0> has been released [1] as Type A, ready for download [2] and as Maven dependences [3].
   
   The branch 'master' has been set to <next release version, e.g. 7.0.0>-SNAPSHOT for development.
   
   Regards,
   <sender name>
   
   [1] https://www.dirigible.io/release/2021/01/31/news_new_release_5_7.html
   [2] http://download.dirigible.io
   [3] https://search.maven.org/#search%7Cga%7C1%7Corg.eclipse.dirigible
   

3. Share via social media:

• https://twitter.com/dirigible_io
• https://news.ycombinator.com/
• https://www.facebook.com/dirigible.io/
• https://www.linkedin.com/groups/8413366/

How-to

Delete Tag:

git tag -d v6.2.0
git push --delete origin v6.2.0

Add new GitHub secret:

Open an issue to the Eclipse Foundation - Help Desk: https://gitlab.eclipse.org/eclipsefdn/helpdesk

Beer

Enjoy!