User Tools

Site Tools


Sidebar

Imprint

kb:bestpractices:wow:releases

Releases

We follow a process when releasing software. This helps us adhere to our own standards, and makes it easier for our customers and the community to find our offerings, identify major versions and keep track of the history of any given software project.

Components

List of Steps

For Automated Builds

executables, installers or source distributions

  1. create new version (release or hotfix) through gitflow
  2. push repo to origin
    1. this will trigger the CI chain if configured

Verify that the release automation succeeded and the corresponding DokuWiki releases page shows the download link to the latest version.

For VI Packages

  1. create new version (release or hotfix) branch through gitflow
    1. for hotfix, implement changes
  2. create VI Package
  3. test VI Package
  4. commit VI Package and VIPB configuration
  5. finish the release/hotfix
  6. push repo to origin
    1. this will trigger the CI chain if configured
  7. use the GitLab API for LabVIEW to
    1. create a new release
    2. create an asset (link) to the .vip in the master branch
  8. copy the .vip to the corresponding release directory on COMP-NAS:releases

Verify that both the release asset on GitLab.com and the corresponding DokuWiki releases page show the download link to the .vip file.

kb/bestpractices/wow/releases.txt · Last modified: 2020/06/08 11:09 by manuel.sebald