On Sun, Dec 15, 2024 at 5:22 PM Nathan Hartman <hartman.nat...@gmail.com> wrote: > > Hi everyone, > > I'd like to start a conversation about getting 1.15.0 released. > > Why a 1.15.0 release: Much work has taken place on trunk since 1.14.0 > and I think it is good for SVN's users, and for our own project > planning, to get the new features released. > > You might have noticed me dabbling in the 1.15 release notes in > staging recently. :-) Right now, trunk has: > * Pristines On Demand > * Multi-WC > * Streamy Checkouts > * New CMake build > > I asked myself, where to start the discussion? > > I think the first question is which type of release should we plan > for, Regular or LTS? > > Paraphrasing our roadmap [1]: > > * Regular releases are supported 6 months. > > * LTS releases are supported at least 4 years and at least 3 months > after the next LTS. > > Currently one LTS line is supported: 1.14.0 was announced in May 2020, > so it honored 4 years of support earlier this year, and support > continues until 3 months after the next LTS release. > > If 1.15.0 is Regular, then 1.14.x support will outlive 1.15.0, and > continue until 3 months beyond the next LTS. That could be 1.16.0 or > later. > > If 1.15.0 is LTS, then 3 months after 1.15.0, the 1.14.x release line > can become EOL. > > Of course, there are many things to consider for a 1.15.0 release. I'm > asking this question first because choosing a release type helps set > expectations and affects further decisions... > > Also, I know that any discussion about 1.15.0 can pull in some... (how > shall I phrase it?) controversial issues. I personally had some strong > feelings in the past but I'm leaving them in the past to focus on the > greater good. I hope that can be the theme. > > [1] https://subversion.apache.org/roadmap.html#release-planning > > Please share your thoughts... > > Nathan
Hi Nathan and SVN devs, I think that it's an excellent idea to start/plan the 1.15.0 release. I think that we should get all these features released, because there weren't any minor versions released for over 4 years, with a huge amount of work done in the trunk. In my opinion, 1.15.0 should be a regular release, due to many upcoming features that may require a fix, which couldn't be done with a patch release. For example, if we would have an issue in the "Pristines On Demand" that requires a new WC format. In this case, it may get fixed in a few months later, with the 1.16.0 release. I have an additional argument for getting 1.15.0 out at the current moment; As we are planning a new feature (xpatch), which needs a major refactoring with the "apply" processor, it's seems to be very nice to release the features we have in the 'trunk' before, since the merge could be destabilized, requiring some testing. In other words, I think that it's better to delay the xpatch feature for the version 1.16.0, so we wouldn't over complicate it. This means that we have to wait a while with the most major changes, related to xpatching, before 1.15.0 is out. Additionally, I think we should ask ourselves about the stuff that we need to finish before getting the trunk out. Do we have such? I'll do this revision for the CMake builds system support soon. There are some unfinished functionalities and the features that I want to have in 1.15.0. Thanks! -- Timofei Zhakov
