Skip to content
GitLab

Release process checklist · Changes

Page history
add note on tagging beta release from develop authored by Peter Krautzberger's avatar Peter Krautzberger
Show whitespace changes
Inline Side-by-side
Release-process-checklist.md
View page @ a8353dcb
......@@ -9,8 +9,8 @@
3. Double check that MathJax's internal version and `package.json` is updated as well.
4. Don't forget to repack and recombine the files before merging.
5. Complete the [[Documentation update process]].
5. Once the `mathjax/develop` branch is deemed ready, it is merged into the `mathjax/master` (for out-of-line patch releases it is also merged into the branch of the minor version).
4. The release is tagged on GitHub with a tag name such as `N.m.p-beta.0`; follow the example of preceding release notes.
5. For non-beta releases, when the `mathjax/develop` branch is deemed ready, it is merged into the `mathjax/master` (for out-of-line patch releases it is also merged into the branch of the minor version).
4. The release is tagged on GitHub with a tag name such as `N.m.p` (for beta releases, we tag from `develop`); follow the example of preceding release notes.
6. The distribution should then be downloaded and smoke tested.
### At CDN
......