-
Notifications
You must be signed in to change notification settings - Fork 32
Release Process
Rich edited this page Jan 30, 2017
·
2 revisions
- Check patch tracker for any patches that should be applied.
- Fix as many bugs from bug tracker as possible.
- Check for/fix memory leaks/errors.
- Review if the documentation is up to date
- Write upgrade guide / user visible changes Changelog
- Make sure sonames and are correct.
- Make sure version is correct
- Check Changelog
- Confirm update guide exists if needed
- If it is a N.X release, create a release-N-X-patches branch in git
- Merge changes from master to release-N-X-patches
- Create a git tag for the release on the release-N-X-patches branch
- Produce dist tar.gz and upload to github
- Produce Windows installer and upload to github
- Rebuild and upload documentation
- Update news on playerproject.github.io
- Update wiki
- Announce release on mailing list
- Request package update on debian/ubuntu/fedora
- Bump soname and version in git so that git builds are distinct from current release