Talend UI Workflow

This document describes the release life cycle.

Talend/ui use changeset so release are on demand. You must add changeset file using the yarn changeset command from the root of the repository and anwer questions.

Problem

Projects rely on given version of dependencies, and to get a bugfix, they have to get all the new features commits with possible breaking changes in them if major release has been done.

We still want to encourage the regular update. We use branches to contribute, here is how.

master

master branch is in an unstable state. It's a protected branch, you must create a PR to merge into it.

Pre-releases are not possible due to CDN infrastructure and tooling. But you can ask for an upload of a PR on the dev CDN to test your PR in an existing project, thanks to sessionStorage with the CDN inject.js script.

Release are done when people approve the release PR.

maintenance/*

Process under discussion

Major / Breaking changes

Breaking changes are prepared and thanks to talend-scripts publish:local script we can test them before merge. The main idea here is to ensure the breaking change is not commited too soon.

We are tring to avoid breaking changes and be sure they have been enough tested and discussed before pushed.