Proper release process #57

New issue

Closed

opened 2023-06-20 18:18:40 +02:00 by migration-script · 0 comments

migration-script commented

2023-06-20 18:18:40 +02:00

Story

As a ds4 developer, I want proper (automatic) release process for new versions so that I can't really make any accidental mistakes when releasing a new version.

Description

As soon as ds4 is provided publicly as a system (and potentially is listed in the official list), we need a proper release process for new versions so that mistakes cannot easily happen. In particular, we need a way to automatically increase all relevant version numbers and download URLs in the manifest file that is reachable under a stable URL. This process should also automatically create the zip file to be downloaded.

Some work has already been done here, in particular zip files are automatically generated with every build anyways.

Acceptance criteria

There is a stable URL to the latest (or latest released?) manifest file.
Pipelines on the master branch include additional manual release jobs in a release stage (last stage) for patch, minor and major versions. Running one of these results in:
- Increase of the version number in package.json and package-lock.json
- Increase of the version number and (potentially adjustment of the download URL) in the manifest under the permanent URL.
- Creation of the downloadable zip at the location where the manifest points to
- creation of a tag with the released version number
Optionally: This process is locally triggerable, too (i.e. not only from pipelines)

# Story As a ds4 developer, I want proper (automatic) release process for new versions so that I can't really make any accidental mistakes when releasing a new version. # Description As soon as ds4 is provided publicly as a system (and potentially is listed in the official list), we need a proper release process for new versions so that mistakes cannot easily happen. In particular, we need a way to automatically increase all relevant version numbers and download URLs in the manifest file that is reachable under a stable URL. This process should also automatically create the zip file to be downloaded. Some work has already been done here, in particular zip files are automatically generated with every build anyways. # Acceptance criteria 1. There is a stable URL to the latest (or latest released?) manifest file. 2. Pipelines on the master branch include additional manual release jobs in a release stage (last stage) for patch, minor and major versions. Running one of these results in: - Increase of the version number in package.json and package-lock.json - Increase of the version number and (potentially adjustment of the download URL) in the manifest under the permanent URL. - Creation of the downloadable zip at the location where the manifest points to - creation of a tag with the released version number 3. Optionally: This process is locally triggerable, too (i.e. not only from pipelines)