Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search


Revision as of 04:16, 22 June 2021 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

EASE is based on a maven/tycho build.

Manual Build

The build requires to have git and maven installed.


git clone
cd org.eclipse.ease.core
mvn clean install

After the build is finished, there is a local update site available from releng/org.eclipse.ease.releng.p2/target/repository

EASE Modules

git clone
cd org.eclipse.ease.modules
mvn clean install

After the build is finished, there is a local update site available from releng/org.eclipse.ease.modules.releng.p2/target/repository

Integration Server

The main hudson integration server is available at:

Release Process

Integrate pending patchsets:

  1. search for open gerrit topics
  2. integrate patchsets for release

Build binaries:

  1. run the release build job

Create release tags:

  1. make sure your git repos are up to date
  2. Switch to 'Git Repositories' view
  3. select <Repository>/Tags
  4. select context menu 'Create Tag...'
  5. set Tag name to 'ease-0.x.0', set Tag message to 'release 0.x.0' (adapt major/minor version)
  6. click 'Create Tag and Start Push...', finish the wizard
  7. repeat procedure for all repositories:

Maintain Bugzilla:

  1. verify that bugs are in CLOSED state and not ony RESOLVED (find resolved bugs)
  2. verify that Target Milestone is set to the upcoming release name (find bugs not related to a milestone)

Maintain Release Description:

  1. switch to
  2. open the upcoming release and maintain release information

Follow the Eclipse release process:

  1. create an automated IP Log for EASE
  2. verify that the log is correct and send it by pushing the Submit For Review button. You will receive a link to a CQ on the following page. That link will be needed in the next steps.
  3. once the IP log is submitted, development on the master branch may continue
  4. send an email to mailing list, requesting release approval.
Subject: PMC approval request for EASE v0.7.0 release
Dear PMCs,

I would like to request your approval for the upcoming EASE v0.7.0 release [1]

The project's IP Log has been submitted [2].


  1. wait for the IP log and PMC approval

Schedule the review

See Review Process

  1. switch to the release page, select the release and select 'Schedule a review for this release.'

Create & update release binaries:

  1. run ease-release on the Hudson server. Building is save and does not alter official download locations. Build will run from master branch by default. If you want to build from a release branch, the job needs to be adapted.
  2. on a failure: fix the problem, back to step 1
  3. promote the build and set the version parameter correctly (eg 0.5.3). After promotion the update sites and download locations are updated and live.
  4. on a failure: fix the problem, back to step 1
  5. create a tag named ease_${version} (eg ease_0.5.3) for each of the following repositories:
  6. push created tags
  7. update the Release Notes wiki page
  8. update the download/index.php page location
  9. add a news entry to the news folder
  10. post an update to the mailing list

Prepare next release:

  1. create a bugzilla entry titled: Release preparations for v0.7.0
  2. update plugin/feature versions to next revision (0.8.0 -> 0.9.0); best use search/replace on the whole workspace
    • search/replace '<version>0.8.0-SNAPSHOT</version>' for pom.xml files
    • search/replace 'Bundle-Version: 0.8.0.qualifier' for MANIFEST.MF files
    • search/replace 'version="0.8.0.qualifier"' for feature.xml files
    • also update /plugins/pom.xml, /features/pom.xml, tests/pom.xml files
  3. create a new release on the EASE project page (sidebar: Committer Tools)
  4. update product roadmap
  5. maintain bugzilla
    • switch to the my account page
    • select 'Bugzilla Manager' from the Committer Tools
    • select 'Edit' from Bugzilla Management
    • add a new Bugzilla version using the release name (eg. 0.5.3)
    • add a new Bugzilla milestone for the upcoming version (eg. 0.6.0). Make sure the Sort key is smaller than the one from the previous release. This will list the upcomping release on the topmost position of the drop down dialog.

Back to the top