Author: dsahlberg Date: Mon Feb 23 07:02:09 2026 New Revision: 1931999 Log: In site/staging:
Followup to r1931988: Remove the detailed instructions about which backport branches usually are supported, since the new release policy may have none or many currently supported releases. * docs/community-guide/releasing.part.html (releasing-announce): As above Modified: subversion/site/staging/docs/community-guide/releasing.part.html Modified: subversion/site/staging/docs/community-guide/releasing.part.html ============================================================================== --- subversion/site/staging/docs/community-guide/releasing.part.html Mon Feb 23 06:54:19 2026 (r1931998) +++ subversion/site/staging/docs/community-guide/releasing.part.html Mon Feb 23 07:02:09 2026 (r1931999) @@ -1417,9 +1417,7 @@ be contacted via the announce-owner@ han <p>If this is an X.Y.0 release, update the community support level at the very top of the <tt>STATUS</tt> files of any branches that have changed support -status. This would usually be <tt>X.Y.x/STATUS</tt>, -<tt>X.$((Y-1)).x/STATUS</tt>, and if the new release is an LTS release, then -the oldest supported LTS branch's <tt>STATUS</tt> file as well.</p> +status.</p> </div> <!-- releasing-announce -->
