Versions Compared

Old Version 28

changes.mady.by.user Leonard Xu

Saved on

compared with

New Version 29

changes.mady.by.user Matthias Pohl

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To prepare for each release, you should audit the project status in the JIRA issue tracker, and do necessary bookkeeping. Finally, you should create a release branch from which individual release candidates will be built.

There was a change being made to the way how the flink-shaded releases are organized within git due to the fact that bugfix releases happen quite rarely. Changes were only performed on master. x.0 releases would be created by tagging the relevant commit on the master branch. This was done to reduce unnecessary effort. If it comes to a point where a bugfix release becomes necessary, one should go ahead and create a release branch release-x.0  (to match the naming scheme of the past branches) which should be based on the tag with the same name release-x.0.

Info

Branches are prefered by git in case of name collisions, i.e. git checkout release-13.0  will always check out the branch. The following command can be used to refer to the tag: git checkout refs/tags/release-13.0 .

One-time setup instructions

...