Skip to content

Release

Jump to bottom
Jimmy Somsanith edited this page Aug 24, 2020 · 11 revisions

Who can do a release:

This process must be done by one of the admins

  • jmfrancois
  • jsomsanith
  • sromain
  • sgangnant
  • vbocquet
  • gjouannic

How to

The release process is done by a github action. The workflow is available here. It has 3 steps

Build

  • install dependencies
  • run tests

Publish

  • publish lerna packages with the current version in each package.json, if they are not already published

Tag and demo

  • create a release tag with the changelog
  • create the demo and publish it to <version>.talend.surge.sh (ex: 5_11_0.talend.surge.sh)

Prepare a new release

  1. Checkout master and bump version. Example here is with a minor version
> git pull origin master
> yarn bump-version minor
  1. Push a new branch
> git checkout -b `<username>/chore/release_<version>` (ex: `jsomsanith/chore/release_5_12_0`)
> git add .
> git commit -m 'chore: release <versions>' (ex: `chore: release v5.12.0`)
> git push origin <branch_name>
  1. Create a Pull Request

Trigger the new release

  1. To run the github action, just merge the release PR.

  2. Check the changelog in the release tag. If the commit message is not well formatted, it can end up in the wrong part.

i18n

After release, go to Jenkins Doc > i18n-product

  1. Click on build with parameters
  2. Fill projects: tui, action: push the messages to the Translation team, branch: master
  3. Click on Build
  4. Follow slack #localization-ui channel to see the translation progress
  5. When it's ready, run the jenkins job again with action: Retrieve translated messages to publish it
Clone this wiki locally