|
|
|
## For releases
|
|
|
|
|
|
### At GitHub
|
|
### At GitHub
|
|
|
|
|
|
1. All code changes are internally tested according to the MathJax [[Development Process]], and merged into the `mathjax/master` branch at GitHub. Repack and recombine the files to make sure they are consistent with the unpacked versions.
|
|
1. All code changes are internally tested according to the MathJax [[Development Process]], and merged into the `mathjax/master` branch at GitHub. Repack and recombine the files to make sure they are consistent with the unpacked versions.
|
|
2. If this is a numbered release, the `vN.M-latest` branch is created, and a README-branch.txt file is made for the version number, and committed to the branch. This makes the branch appear as a separate line in the network viewer.
|
|
2. If this is a numbered release, the `vN.M-latest` branch is created, and a README-branch.txt file is made for the version number, and committed to the branch. This makes the branch appear as a separate line in the network viewer. Check that MathJax's internal version is updated as well.
|
|
3. The release is tagged in GitHub. This causes a labeled distribution to be created (with the tag name) in the GitHub download manager.
|
|
3. The release is tagged in GitHub. This causes a labeled distribution to be created (with the tag name) in the GitHub download manager.
|
|
3. Complete the [[Documentation update process]].
|
|
3. Complete the [[Documentation update process]].
|
|
4. The download distribution should then be downloaded and smoke tested.
|
|
4. The download distribution should then be downloaded and smoke tested.
|
... | @@ -27,3 +29,31 @@ |
... | @@ -27,3 +29,31 @@ |
|
* Announcement should be posted to the User Groups at mathjax-dev and mathjax-users
|
|
* Announcement should be posted to the User Groups at mathjax-dev and mathjax-users
|
|
* Advise regarding the CDN propagation (clear browser cache etc)
|
|
* Advise regarding the CDN propagation (clear browser cache etc)
|
|
* The new post should be announced on social media channels [[MathJax-web-presence]].
|
|
* The new post should be announced on social media channels [[MathJax-web-presence]].
|
|
|
|
|
|
|
|
|
|
|
|
## For a beta releases
|
|
|
|
|
|
|
|
This is almost identical, except that we don't do as much.
|
|
|
|
|
|
|
|
### At GitHub
|
|
|
|
|
|
|
|
1. All code changes are internally tested according to the MathJax [[Development Process]] and merged into the `mathjax/vN.M-beta` branch at GitHub. Repack and recombine the files to make sure they are consistent with the unpacked versions.
|
|
|
|
2. The `vN.M-beta` branch is created. This makes the branch appear as a separate line in the network viewer. Check that MathJax's internal version is updated as well.
|
|
|
|
4. The download distribution should then be downloaded and smoke tested.
|
|
|
|
|
|
|
|
### At CDN
|
|
|
|
|
|
|
|
1. Upload the new version to the CDN as `vN.M-beta` (and while you're at it, create `vN.M-latest`).
|
|
|
|
1. Set the custom headers for the fonts (see [[Managing Rackspace Cloud Files & CDN]])
|
|
|
|
|
|
|
|
### At mathjax.org
|
|
|
|
|
|
|
|
2. A news announcement for the release is posted. The post should
|
|
|
|
* Describe what is new
|
|
|
|
* Point to the beta branch and download at github.
|
|
|
|
* Give instructions for reporting bugs, and refer questions to MathJax User Groups
|
|
|
|
|
|
|
|
### For the community
|
|
|
|
|
|
|
|
* Announcement should be posted to the User Groups at mathjax-dev and mathjax-users
|
|
|
|
* The new post should be announced on social media channels [[MathJax-web-presence]]. |
|
|
|
\ No newline at end of file |