Maintaining

Notes for Video.js project maintainers

RELEASING

The video.js release process is outlined below. Only core contributors to video.js can create a new release but we do them very regularly. If you're just looking to get involved with the project, head over to the contribution guide for tips on how to get started.

Patch Releases

• Merge from stable to patch
• Push from patch to upstream
• Log into codeship.io and watch the publishing process
• Checkout and update stable
• Run npm i
• Make sure npm ls --depth=0 output has versions matching the package.json
• Run grunt to create build/cdn
• Upload CDN files to AWS minor/patch locations
  • Currently, you need @heff to do this
  • If you had credentials, you would run grunt aws_s3:minor. Why minor? The grunt task updates the files at the version level you specified. When you release a new patch, you want anyone using "4.12/*" URLs to pick it up.
• Log into fastly.com and purge the CDN
  • Go to "Configure"
  • Click Purge
  • Add the path you'd like to purge. For example, "4.12/video.js", "4.12/video-js.css", and "4.12/video-js.swf" You're done!