Skip to content
GitLab

Documentation update process · Changes

Page history
Update for v2.7 authored by Peter Krautzberger's avatar Peter Krautzberger
Show whitespace changes
Inline Side-by-side
Documentation-update-process.md
View page @ e937dd8a
...@@ -29,11 +29,9 @@ When you save your changes version, GitHub automatically creates a fork (if it d ...@@ -29,11 +29,9 @@ When you save your changes version, GitHub automatically creates a fork (if it d
* Create a "What's new"-page for the new release. * Create a "What's new"-page for the new release.
* Document all new features. * Document all new features.
* Note: The `master` branch will always be the one to keep up-to-date, being visible at docs.mathjax.org/en/latest. * Note: The `master` branch will always be the one to keep up-to-date, being visible at docs.mathjax.org/en/latest.
1. When everything is finished, make a pull request to merge `vN.m-latest` back into `master`. 1. Upon release, merge `vN.m-latest` back into `master`.
1. Check if docs.mathjax.org has successfully built `vN.m-latest` and `master` at docs.mathjax.org 1. Check if docs.mathjax.org has successfully built `vN.m-latest` and `master` at docs.mathjax.org
### Release process checklist -- git version ### Release process checklist -- git version
0. This is part of the [[Release process checklist]]. The first few items could be done before the beta launch. 0. This is part of the [[Release process checklist]]. The first few items could be done before the beta launch.
......