Creating releases

General information

To get a better overview of technical changes, we use releases in regular intervals. Releases automatically include everything on the branch (until the last commit). The releases have a set title structure: v1.2.3

The title is divided into three levels, according to the significance of the changes:

• Minor changes (e.g. Minor design changes, small bugs; last number)
• Normal changes (e.g. new features; number in the middle)
• Major changes (e.g. new framework; first number)

The most typical one for us is the second one. Create the title of the new release by increasing the relevant level by one.

Note: Releases are only used for technical changes. Do not use releases to publish a blog post.

Creating a new release

1. Make a new pull request on the repo.
   Note: Choose develop as base and compare to your current sprint branch.

   • Create the title as mentioned above
   • Use the comment section to enter a list of the related changes

2. Merge the pull request (either by Unai M., Unai A., Christoph or Birgit)

3. Make a new pull request on the repo.
   Note: Choose master as base and compare to develop.

   • Take the same title as in step 1
   • Use the comment section to enter the change list from step 1

4. Merge the pull request (either by Unai M., Unai A., Christoph or Birgit)

5. Go to the release tab.

6. Click on "Draft a new release"

   • Take the PR title as Tag version
   • Choose @master as your target
   • Adapt your title to the following structure: Release Title of the PR, e.g. Release v1.2.3
   • Copy your change list from the comment section of your PR and paste it into the description section

7. Press "Publish release"