Re: Branches

(Dropping pmc@ to avoid cross posting. Feel free to bcc)

Do we have a clearly documented support schedule now that were're on 
real semantic versioning?

I would expect to have a support branch for each not EOLed, thus 
supported, major / minor combination. I've always regarded this a best 
practice I follow, and most of the project I'm aware of. This also gives 
clear expectations for users, making clear which release lines are 
supposed to get at least bugfixes.

Do we expect to release patches for 6.1? Rather not, do we?

What about 6.7 and 6.8? Sounds more legit to me, at least for an 
important security fix.

But even if we say only the last minor version in 6 is supposed to get 
updates, naming the only branch besides main "support/6.8.x" rather than 
"support/6.x" expresses our intentions more clearly. In addition, we're 
still able to have two or more supported branches within the same major 
line if this is anyhow required, without breaking our naming conventions 
and the expectations of our users.

- René

Am 02.03.26 um 15:46 schrieb Lukasz Lenart:
> Hi,
>
> I'm going to simplify branch structure and keep just two branches:
> - main -> Struts 7.x
> - support/6.x -> Struts 6.x
>
> Any objections?
>
>
> Cheers
> Łukasz

-- 
René Gielen
https://about.me/rgielen