Release Management

This page documents the process for creating a DASH.js release. An official DASH.js release needs to be approved by the DASH-IF Interoperability Working Group. This page documents how this approval is sought and, once provided, how a formal release of the DASH.js code is made.

1. Development 1. Agree the features that will be in the upcoming release 1. Create a feature branch for each major feature 1. Minor changes can be made in hotfix branches 1. Request review of feature branches to be included
   1. Issues to be raised in the issue tracker
   2. Reviews must include a Licence Audit and Legal Audit - including headers, dependencies, LICENCE and NOTICE files
   3. After successful review merge the feature branch into the "next" branch 1. When all feature branches have been merged into next and no blocking issues in the release are remaining release process can start
2. Prepare for release 1. Bump the version number in the "next" branch 1. Conduct a licence Audit and Legal Audit - including headers, dependencies, LICENCE and NOTICE files 1. Documentation – Check installation and build documentation for accuracy, create status document, create release notes 1. Call for developers to test the "next" branch
   1. Note that from this moment until next is merged into master only bug fixes are allowed in "next" 1. Call a vote for the release
3. Create release candidate 1. Build the release packages 1. Request that the DASH-IF Interoperability Working Group test and approve the release candidate
   1. If approved proceed, otherwise go back and fix issues raised 1. Merge "next" into "master" 1. Tag master 1. Write the release announcement (with approval from press@) 1. Build the release files 4.Release 1. Upload release files to the distributions site 1. Update the website
   2. News item
   3. Demo updates 1. Announce the release