On Tue, Jul 14, 2026 at 12:38 PM Evgeny Kotkov <[email protected]> wrote:
> Timofei Zhakov <[email protected]> writes: > > > How exactly are we planning to roll the final release? I mean in a sense > > AFAIK according to the policy we need two official RC's to be released > > before. Am I missing something? > > The core concept for .0 release is the "soak" period. Once the first > public > RC is out, we start a four-week soak. > > The process is described here, with a really helpful diagram: > > https://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization-overview > https://subversion.apache.org/docs/community-guide/svn-soak-management.png > > If there are no blockers requiring destabilizing fixes, the whole process > can be as simple as "ship one RC, wait four weeks, then ship a final build > identical to that RC", deferring everything else to a .1 patch release. > > In other words, we don't necessarily need an RC4 build if no critical > problems are found in RC3. > > We may, however, want to roll a newer release candidate with some of the > non-destabilizing fixes merged, if we think it makes sense for them to be > in 1.15.0 rather than 1.15.1. In that case we would publish RC4, RC5, and > so on. Once the soak ends, the latest RC becomes the final 1.15.0 build. Thanks for explaining! I don't know where I get that from, I guess because we indeed need one but the amount of RC's we already had confused me. -- Timofei Zhakov
