Re: Subversion 1.15.0-rc3 up for testing/signing

On 14. 7. 2026 09:21, Daniel Sahlberg wrote:
>
>
> mån 13 juli 2026 kl. 22:14 skrev Timofei Zhakov <[email protected]>:
>
>     On Mon, Jul 13, 2026 at 1:38 PM Evgeny Kotkov via dev
>     <[email protected]> wrote:
>
>         The 1.15.0-rc3 release artifacts are now available for
>         testing/signing.
>         Please get the tarballs from
>         https://dist.apache.org/repos/dist/dev/subversion
>         and add your signatures there.
>
>         Thanks!
>
>     I'll soon go ahead and do the testing. Just have a small question
>     to clarify;
>
>     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?
>
>
> From what I understand I HACKING [1], there is no requirement of a 
> specific number of RC’s: ”If no serious bugs are found, the -rc tag 
> will be dropped, and the contents of this release will be declared 
> stable.”

I recall no minimum required RC versions. Nor are we required to createe 
-alpha or -beta versions. It's up to the RM and PMC to decide.

>
>
>     So this hopefully must be the first one we roll out, then we'll
>     have rc4 and 1.15.0, right? Also of course if we have something we
>     need to follow up we'll skip a version but it doesn't change the
>     point all that much.
>
>     I think it's important because there are still some nominations in
>     the stable branch so all the blockers are merged by the right moment.
>
>
> I would prefer if we get 1.15 out of the door even if there are still 
> nominations. I don’t think they are critical and getting the release 
> done seems like a priority right now.


The important nominations have been merged. I see one that is a 
potential improvement, but it doesn't fix a regression against 1.14. All 
three currently in STATUS are nice-to-have. Only the last one (Make `svn 
--version -v` report actual character encoding used on Windows) is a 
1.15.0 feature, given that it affects the UI. Or it could be treated as 
a bug and merged for .1 etc.

-- Brane