Release Procedure

Dash.js Release Procedure

Pre-release: (Post Code Freeze Date)

• Create a new release candidate for all changes pulled into development (even if they are minor).
• The release candidate should be a branch named RC_vX.X.X not a tag.
• Create Release Notes and share on mailing list for feedback.

Release

• Merge Development into master. Developement should be the same exact state as the Latest RC Branch.
• Once Master is merged pull it locally and build DIST files.
• Push DIST Files to master.
• Use GIT Release UI to draft a release.
  • Tag the release with the version number. vx.x.x
  • Add Release Notes created before hand.
  • Save as Draft for now.
• Ask Will Law to pull master and run grunt to build JSDocs with cmd "grunt jsdoc"
  • Ask Will to upload JSDoc and Min files to cdn.dashif.org under vx.x.x
• Publish Release by going to saved draft and clicking publish.
• Get Tag release URL and Send out officail Dash.js Release Email (Template Below)
• Delete All RC Branches for cleanup

Email Template

Hello All, 

We are pleased to announce that a new version of Dash.js has been released!  
A big thank you to all the contributors that made this release possible!
  
Release Info Here:
https://github.com/Dash-Industry-Forum/dash.js/releases/tag/v

The latest minified files have been hosted on a global CDN and are free to use in production. 
The “latest” branch will be updated with each release to point to the latest content. 
The branches tagged with a specific release will never change once archived. 

Latest:
http://cdn.dashjs.org/latest/dash.all.js
http://cdn.dashjs.org/latest/dash.debug.js
http://cdn.dashjs.org/latest/dash.min.js

v
http://cdn.dashjs.org/v/dash.all.js
http://cdn.dashjs.org/v/dash.debug.js
http://cdn.dashjs.org/v/dash.min.js

The latest docs are also available here:
http://cdn.dashjs.org/latest/jsdocs/MediaPlayer.html

DASH-IF Hosted Player:
http://dashif.org/reference/players/javascript/v/samples/dash-if-reference-player/index.html

Release Notes