Den sön 22 feb. 2026 kl 21:16 skrev Nathan Hartman <[email protected]
>:

> On Sun, Feb 22, 2026 at 2:49 PM Daniel Sahlberg <
> [email protected]> wrote:
>
>> Den fre 20 feb. 2026 kl 13:06 skrev Evgeny Kotkov <
>> [email protected]>:
>>
>>> Daniel Sahlberg <[email protected]> writes:
>>>
>>> > I would have suggested to support the previous release for 6 month
>>> instead
>>> > of 3 (to make sure any distributions with a twice-per-year release
>>> policy
>>> > have a chance to pick up the new minor release)
>>>
>>> Agreed, let's use a 6-month support period instead of 3 for this part.
>>>
>>> With the positive feedback in this thread, I'll consider the new policy
>>> in
>>> place and will gradually move forward with it for the 1.15 release.
>>>
>>
>>> Thanks,
>>> Evgeny Kotkov
>>
>>
>> Thank you for driving this forward!
>>
>> I have tried to update the staging website in r1931988. See
>> https://subversion-staging.apache.org/roadmap.html#support-period
>>
>
>
> Looks good to me! Thanks for doing that.
>
>
> When reviewing the website, I saw that we differentiate between how many
>> votes are required for backports between LTS and regular releases, see
>> http://svn_staging/docs/community-guide/releasing.html#release-stabilization-how-many-votes
>>
>
>
> Corrected link:
>
> https://subversion-staging.apache.org/docs/community-guide/releasing.html#release-stabilization-how-many-votes
>

Oh.. I leaked my internal dev-server :-)


>
> I will assume we apply the LTS requirement for all new releases - ie 3
>> votes required and update HACKING, unless someone chime in during the next
>> few days.
>>
>
>
> I'm OK with that. The text about regular releases can just be omitted
> here, since it doesn't apply to any supported release lines.
>

I've committed this to the staging site in r1931998. I also made a minor
tweak to the release announcing process (r1931999) and removed the text
about 1.15 being a regular release (r1932000).

1931988 to 1931999 could be merged to publish, while 1932000 will be
included in the actual release.

Cheers,
Daniel

Reply via email to