We are not yet in development freeze -- new features and bugfixes are still freely accepted into develop.
A blocker list for v0.8 has not yet been started.
Associated branch(es) to the current release candidates should be named vx.y.z-rcn, where vx.y.z corresponds to the version ID in the title and n is the release candidate ID, starting from 1.
Once all blockers are resolved and a development freeze initiated, the below summarises the release procedure.
Loop start (loop count is n):
If unsuccessful:
- fix bugs in separate issues / MRs that merge into develop
- rebase vx.y.z-rc
n unto develop and rename it to vx.y.z-rcn+1
- uncheck all checked boxes above and restart loop
If successful:
Testing TODOs:
We are not yet in development freeze -- new features and bugfixes are still freely accepted into
develop.A blocker list for v0.8 has not yet been started.
Associated branch(es) to the current release candidates should be named
vx.y.z-rcn, where vx.y.z corresponds to the version ID in the title andnis the release candidate ID, starting from 1.Once all blockers are resolved and a development freeze initiated, the below summarises the release procedure.
Loop start (loop count is
n):n-1and the current rcn. (Let rc0bedevelop.)n(see below for ``sub-checklist'')If unsuccessful:
nunto develop and rename it to vx.y.z-rcn+1If successful:
ninto developTesting TODOs: