Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
- Consider, which changes (aka commits) you want to release into master (This commit comparison view is quite useful)
- Determine the new version number, following semantic versioning spec.
- Move the relevant commits into a new branch
release/x.x.x[using this git flow technique] (http://mclear.co.uk/2012/10/03/using-git-flow-to-release-new-version/)
- Ensure, all version numbers are up-to-date
- Be sure the API version is correct (new endpoints shouldn't be added to already existing API versions)
- Update the version number in
- Create a new entry in the changelog, documenting all changes.
- Open a pull request from
- Once the pull request is merged into master, tag the merge commit with
- Create a new windows build
- Name the resulting zip file:
- Add the file here for the etherpad.org website: ether.github.com/downloads
- Update the docs
- Build the docs with
- Put the contents of
out/doc/into a new directory
- Adjust all links on ether.github.com
- Update the version numbers on all download buttons
- Update the documentation link (version number in url and text) on the website
- Push ether.github.com to github
- Update links in this wiki also
- Put up some notices on relevant sites, announcing the new release as well as possibly critical changes it introduces.
- Pull master branch over develop
- Update the beta.etherpad.org instance using git pull
Note that step 15 is for Etherpad Site Admins
Clone this wiki locally
Press h to open a hovercard with more details.