Always subject to change, see also the roadmap.
roughly 2 months:
- ticket review and planning: updating the new milestone page
- code refactoring and cleanups early
- beta builds
- run automated tests
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
a few weeks at most - bug fixes only:
Maintenance / Stable 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.