<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><font face="monospace">On 23/1/25
03:06, Albert Astals Cid wrote:<br>
</font></div>
<blockquote type="cite" cite="mid:4951588.GXAFRqVoOG@xps15">
<pre wrap="" class="moz-quote-pre">El dimecres, 22 de gener del 2025, a les 4:35:53 (Hora estàndard del Centre
d’Europa), <a class="moz-txt-link-abbreviated" href="mailto:rhkramer@gmail.com">rhkramer@gmail.com</a> va escriure:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">On Tuesday, January 21, 2025 05:16:25 PM Albert Astals Cid wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Is it not a consequence from the fact that there's no more releases
planned?
It's weird to say "for things that we don't plan releases there will no be
releases"
What would you write?
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
>From the peanut gallery: How about:
No more releases planned for this project.
and perhaps, in parenthesis after that, something like (end of project)
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
But we're not speaking about end of project.
We are speaking about the fact that Okular 24.12.x is not going to be released
anymore because Okular 25.04.x is the next release series, not that we're not
going to release Okular at all anymore.
Cheers,
Albert
</pre>
</blockquote>
<p><font face="monospace">I guess I should try to expand on my
thoughts before throwing my ideas at the mailing list.</font></p>
<p><font face="monospace">I think my original thought was several
fold:</font></p>
<p><font face="monospace">1. How long/which version (tied together
as our releases are done at regular intervals) do we support
each release for things KDE produces, e.g. Gear, Plasma,
Frameworks?</font></p>
<p><font face="monospace">2. Document this information clearly on
our Wiki.</font></p>
<p><font face="monospace">3. On the documentation side, have a
single Wiki page per release type (Gear, Frameworks, Plasma)
that details this.</font></p>
<p><font face="monospace">for example:<br>
</font></p>
<p><font face="monospace">Gear</font></p>
<p><font face="monospace">Current supported versions: 24.12.*<br>
</font></p>
<p><font face="monospace">Version Release Date
Supported</font></p>
<p><font face="monospace">==================================================</font></p>
<p><font face="monospace">24.12 Released 19th December 2024
Yes<br>
</font></p>
<p><font face="monospace">24.08 Released 5th August 2024
End of Life*<br>
</font></p>
<p><font face="monospace">...</font></p>
<p><font face="monospace">All the older releases...<br>
</font></p>
<p><font face="monospace"><br>
</font></p>
<p><font face="monospace">* End of Life text would be a link to a
page on the wiki would describe that KDE software is regularly
released and it is always recommended to upgrade to the latest
released version. End of Life software does not receive
important security updates or bug fixes. More text here about
why that is important, etc.<br>
<br>
<br>
I think my goal overall is to set expectations for users and
developers clearly on our wiki. Don't target End of Life
software for development and let users know that versions like
24.08, 24.05, 24.02 etc on LTS type distros are not supported
any longer.<br>
</font></p>
</body>
</html>