Skip to content
GitLab

Release process checklist · Changes

Page history
Fixed typo authored by Davide P. Cervone's avatar Davide P. Cervone
Hide whitespace changes
Inline Side-by-side
Release-process-checklist.md
View page @ d4f8239c
### At GitHub ### At GitHub
1. All code changes are internally tested according to the MathJax [[Development Process]], and merged into the `mathajx/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.
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]].
......