Version 1 (modified by 4 years ago) (diff) | ,
---|
Release Process
Always subject to change, see also the roadmap.
Development Phase
roughly 2 months:
- ticket review and planning: updating the new milestone page
- code refactoring and cleanups early
- beta builds
- run automated tests
Stabilisation Phase
roughly 1 month - much more for LTS releases:
- updating the OSX and win32 builds to the latest versions supported (ie: ffmpeg, pillow, etc..)
- update patches with new offsets
- check profiling results for regressions (see #797)
- add new tests (see #847, #177, #660)
- run with "-d all" and look for exceptions, look for idle events with out any clients connected
- test against the oldest client and server versions supported
- whitespace / tabspace cleanup
- tagging the version in the repository
Release
a few weeks at most - bug fixes only:
- add to wiki/News page
- re-assign unfinished tickets to a later milestone if the work is not completed (excluding testing)
- update wiki/Source and also this page
- send announcements emails
Maintenance Updates
Fixes are almost always committed to trunk before landing in other branches, you can find a list of the currently pending fixes here. The exact schedule of those updates depends mostly on the severity of the issues fixed.