Evgeny Kotkov <[email protected]> writes: > If there are no objections, I plan to start moving things forward shortly. > Hopefully, we can get 1.15 out within the next two to three months.
I have checked the current state of trunk, and I believe we're in good shape. Specifically, there appear to be no loose ends or incomplete new features and the last potentially destabilizing change (r1927953) occurred four months ago. >From the RM perspective, I propose we proceed with creating the 1.15.x branch shortly, and defer any other outstanding items to 1.16.x. This should allow us to keep our focus and attention on various tasks required for 1.15.0. Assuming no objections, I can plan to complete the remaining preparatory steps and create the 1.15.x branch on Monday, December 15th. Below is a detailed status check based on our documented steps [1] for creating a new minor release branch: 🗹 Review the Roadmap. Should any of the outstanding items be addressed before branching? Comment: Personally, I do not think we should be starting any additional features for 1.15 at this stage. 🗹 Review the incumbent stable branch's STATUS file for outstanding -0 and -1 votes. Was code that is going to be included in the new branch objected to? Comment: There are no such votes in 1.14.x/STATUS. ☐ Do any tree-wide, mechanical changes. Comment: I will handle this. ☐ Review new and changed APIs for design and style (e.g. Doxygen mark-up, undocumented parameters, deprecation, public/private status, etc.). Comment: I plan to perform this review and post about it separately. ☐ Run compatibility tests against the incumbent minor release. Comment: I would appreciate assistance with this step. [1]: https://subversion.apache.org/docs/community-guide/releasing.html#before-branching Thanks, Evgeny Kotkov
