|
The plan to increase the release frequency of odlparent is as follows:
- build a job, on top of multipatch (once its pending improvements are merged), which will allow all incoming master patches to be checked against the managed projects to detect pending breakages;
- merge appropriate master patches onto the current maintenance branch (3.1.x) and/or the next minor branch (3.2.x)
- build another job, also on top of multipatch, which will verify that the current tip of the maintenance branch doesn’t break the managed projects;
- release the maintenance branch whenever appropriate.
Longer term, we could imagine extending that to the next major release — if the next major release can be automatically verified (including CSIT), we could perhaps upgrade to it...
The managed projects are now in a state where they can be bumped semi-automatically. The remaining issue there is that merging the patches still involves too much work (for LF releng and/or odlparent committers). The load increases as we near a release since we need version convergence, which means that an oldparent bump involves cascading releases of all release-based projects.
|