Release Management Guidelines

Release Management in SASUnit will be done via Milestones.

Usage of milestones

It should be possible to have milestones that do not lead to a new SASUnit release.
But each release needs to have at least one milestone

Overview of automated processes

When a milestones is completed then the current source code in the main branch shall be published as a new release.
This is done by marking the current commit with a tag.
When a tag is pushed to te remote server the build of the release is triggered. This process is implemented in the workflow "Create Release" (release.yaml). Following steps are carried out:

• Run example project in English and German for Windows and Linux
• Reduce files in the filesystem
• Zip files to build release files for Windows and Linux

Preperations for a new release

Before a new relases is published please check the following:

• If necessary implement SASUnit setup scripts for new environments
• Check if new SASUnit version is updated in init_sasunit.sas
• Check if SASUnit DB version has changed and is correctly impemented in init_sasunit.sas
• ChecK Readme files in repository and wiki
• Write Release Notes (including User's Guide)

Tests to be done before publishing

Once the workflow "Run Tests" (test.yaml) has completed successfully some tests need to be carried out. These are described in detail in the Quality Guidelines

Create and push tag

The name of the tag can be derived from the milestone. Push the tag to the main branch in the private repository.

Back to Development Guidelines