It’s about time for another VTK release. The CI dashboards have been stabilizing fairly well and it seems like a good time to start cutting a release.
Tentative dates:
Jun 15: branch and create rc1
Jun 22: rc2 and bugfix focusing (CI should be solid by this point)
Jun 29: rc3 if needed (final if possible); revert becomes more likely for issues that arise
Jul 6: rc4 if needed (final if possible); platform/compiler fixes only by now
Jul 13: rc5 if needed (final if possible)
Jul 20: final release (if all else fails)
First up, the next release is planned for about 4 months from now (late September/early October) with a similar schedule (see below). So if you miss this release, the next one shouldn’t be too far away. With CI and the robot able to help out more and the release process being more structured, there isn’t as much manual work involved anymore.
Second, it is up to code authors to ping reviewers for MRs. We cannot commit to reviewing everything just because it was submitted, sorry. Please tag MRs with the 9.3 milestone to at least get some metadata wrangling involved.
Third, in order to keep the release under control, as we get closer to the final release, features are likely to be reverted rather than waiting for a fix (waiting for fixes that never happened is why 8.2.1 never got released). If a problem is there on Monday and you can get to it on Thursday, it is likely to be reverted until it can be fixed. In order to bring the change back, running git revert -m1 $merge_commit will undo a merge and can be added to the MR that fixes it up. Alternatively, the branch can just be redone as if from scratch; up to you.
When is the RC1 supposed to be tagged ?
According to the proposed schedule it should be done but I haven’t found anything.
Can we still propose Merge request for 9.3.0 ?