... | ... | @@ -29,6 +29,8 @@ When you save your changes version, GitHub automatically creates a fork (if it d |
|
|
* Create a "What's new"-page for the new release.
|
|
|
* 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.
|
|
|
1. Log into ReadTheDocs and add the `vN.m-latest` branch to the build list.
|
|
|
1. Check if docs.mathjax.org has the new build for v2.2
|
|
|
1. Merge `vN.m-latest` back into `master`.
|
|
|
1. Push `vN.m-latest` and `master` back to github. `git push origin master vN.m-latest`
|
|
|
1. After(!) the release, modify the `vN.m-latest` branch (Note: this branch will have to be updated updated manually but will allow people to have a stable link for documentation of that version)
|
... | ... | @@ -39,7 +41,6 @@ When you save your changes version, GitHub automatically creates a fork (if it d |
|
|
git push origin "vN.m-latest"`.
|
|
|
1. Commit & push pack to github: `git commit -a -m "(log message about version change)" &&
|
|
|
git push origin master`
|
|
|
1. Log into ReadTheDocs and add the `vN.m-latest` branch to the build list.
|
|
|
|
|
|
### Appendix: Understanding the process
|
|
|
|
... | ... | |