Skip to content

Commit f2a93e5

Browse files
committed
Add release procedure
1 parent afcf78f commit f2a93e5

File tree

1 file changed

+29
-0
lines changed

1 file changed

+29
-0
lines changed
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
layout: default
3+
title: Release Procedure
4+
parent: Developers
5+
---
6+
7+
# dash.js Release Procedure
8+
9+
## Pre-release: (Post Code Freeze Date)
10+
* Update version numbers in `package.json`
11+
* Create a new release candidate for all changes pulled into the `development` branch (even if they are minor).
12+
* The release candidate should be a branch named RC_vX.X.X not a tag.
13+
* Create Release Notes and share on Google Groups mailing list for feedback.
14+
15+
## Release
16+
* Merge the `development` branch into the `master` branch. `development` should be the same exact state as the Latest RC Branch.
17+
* Once the changes are merged into the `master` branch pull the `master` branch locally and build `dist` files by running `npm run build`.
18+
* Push the resulting `dist` files to the `master` branch.
19+
* Use the Git Release UI to draft a release.
20+
* Tag the release with the version number, e.g. `vx.x.x`
21+
* Title the release `dash.js vX.X.X`
22+
* Add the release notes created beforehand.
23+
* Save as a draft for now.
24+
* Update and upload the archive index page for the player.
25+
* Publish the Git release by going to saved draft and clicking publish.
26+
* Update NPM https://www.npmjs.com/package/dashjs - Just go to package.json in dash.js in type "npm publish"
27+
* Get Tag release URL and Send out official Dash.js Release Email
28+
* Delete All RC Branches for cleanup
29+

0 commit comments

Comments
 (0)