EOL business

[Harald Sitter]

Servas!

So, at the plasma sprint we decided to have an extra release for -1
(e.g. 6.3), after a new major release (e.g. 6.4), such that we can
actually say -1 is "supported" while distros migrate to current
release (6.4)

Since that is a bit abstract the idea here was that we have

- 6.3.5
- 6.4.0
- (6.3 is now almost out of support)
- 6.3.6
- (6.3 is now out of support because we have no more releases to fix bugs in)

Now to my mind that also meant our bug bot would put that into
practice exactly as described, but on matrix there was some discontent
with this. Let's figure this out.

The messaging involved is thusly:

almost_eol gets a comment with this text
https://invent.kde.org/sysadmin/bugzilla-bot/-/blob/master/data/almost-eol.txt.erb?ref_type=heads

eol gets a comment **and closed** with this text
https://invent.kde.org/sysadmin/bugzilla-bot/-/blob/master/data/eol.txt.erb?ref_type=heads

Now as for timing these we have two options:

a) things happen as described. 6.3.6 marks the end of 6.3 support --
if users want support for 6.3 they have to go to their distro (i.e.
6.3 became almost_eol with the release of 6.4.0 and is as of yesterday
eol)

b) 6.3 becomes eol at an arbitrary point in the future (when?) but we
won't be able to fix bugs. we have to guess or test whether a bug is
applicable for 6.4/master

Suffice to say I am for a) because b) seems to entirely defeat the
purpose of what we set out to do. We'd still get outdated bug reports
and we'd again have people on a release nobody really supports and
everyone shrugging as to who exactly will fix their bugs or care about
their reports.

We could delay a) by a week or so, but that puts extra things to
remember on the release manager's plate, I would avoid that if
possible.

Thoughts?

HS