The reality is that we are a very small team - it is simply not feasible to
maintain that many branches[1].
You are not asking about "time to upgrade" anyway, in my opinion. You are
asking about removing the need to upgrade, which is very different. Us
stopping support for 5.6 does not mean you can no longer use 5.6. It
simply means we (this very tiny team) will no longer back-port changes.
You can continue to use it; and in fact, since it is open source, you can
even continue to do these back-ports yourself.
As for a statement on the website, I'm not sure exactly what that would
look like. Your suggestion is just vague. "X months"? How many months is
that? 2? 24? Big difference. E.g., you realize 6.0 was released exactly
2 months ago to the day right[2][3]? That is "months" already. And I have
already said we will continue to support 5.6 for the time being, so that
will be "months"++. The rest of your statement is in fact exactly what we
do already[4]. I'm not against adding something to the website if it helps
clarify things, but that wording is not it.
P.S. To be fair, by "reduce doubt among Hibernate users" you mean *your*
"doubt". Which is fine, but let's not extrapolate that to all Hibernate
users.
[1] Though really, point me to any project / product the size and
complexity of Hibernate, not to mention user base, that supports as many
code bases for free that you are asking.
[2]
https://in.relation.to/2022/03/31/orm-60-final/
[3] That was 6.0.0.Final. Including CR releases (which I do) its been
many, many months.
[4] 6.0 has been out for months. 6.1 is about to be released. And we are
still supporting 5.6.