[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Synchronized release schedule for Plasma
From:       Timothée_Ravier <travier () redhat ! com>
Date:       2020-11-24 15:07:01
Message-ID: CACStWPBqEEnOYCu4uU0GMypKnDJxWaf-6wfiHZ97Qy7cwotV9w () mail ! gmail ! com
[Download RAW message or body]

Hi KDE/Plasma developers!

Nowadays, Fedora and Kubuntu make new releases twice a year within a week
of each other, with relatively predictable release schedules.

Unfortunately, new KDE/Plasma releases happen a little bit too late for
them to be included in those distributions in time for the release. Thus
the current version of KDE/Plamsa in both Fedora and Kubuntu is one release
behind (at least on release day). It may or may not be updated after the
release.

For the Fedora KDE SIG, we have an issue about this:
https://pagure.io/fedora-kde/SIG/issue/25

As distribution package maintainers, we would like Plasma developers to
slightly alter the release schedule to align releases with a more
distribution friendly cycle. You could consider shortening one release
cycle (and then keep the 6 month schedule) to align releases.

With this schedule in place, we would also benefit from more beta releases
over a slightly longer period. They would be packaged into the beta and RC
releases of those distributions thus enabling more pre-release testing.

All of this would benefit both upstream and downstream:

  - More pre-release and just released software testing as users test the
new distribution version directly with the KDE beta and fresh stable
releases
  - More updated and happy users using the latest release
  - Less bugs reported against older releases, more bugs reported before
the final stable releases

What do you think?

Thanks!

Timothée Ravier for the Fedora KDE SIG

-- 

Timothée Ravier

Red Hat & Fedora CoreOS Engineer

Red Hat <https://www.redhat.com/>

travier@redhat.com    IM: travier
<https://www.redhat.com/>

[Attachment #3 (text/html)]

<div dir="ltr">Hi KDE/Plasma developers!<br><br>Nowadays, Fedora and Kubuntu make new \
releases twice a year within a week of each other, with relatively predictable \
release schedules.<br><br>Unfortunately, new KDE/Plasma releases happen a little bit \
too late for them to be included in those distributions in time for the release. Thus \
the current version of KDE/Plamsa in both Fedora and Kubuntu is one release behind \
(at least on release day). It may or may not be updated after the release.<br><br>For \
the Fedora KDE SIG, we have an issue about this: <a \
href="https://pagure.io/fedora-kde/SIG/issue/25">https://pagure.io/fedora-kde/SIG/issue/25</a><br><br>As \
distribution package maintainers, we would like Plasma developers to slightly alter \
the release schedule to align releases with a more distribution friendly cycle. You \
could consider shortening one release cycle (and then keep the 6 month schedule) to \
align releases.<br><br>With this schedule in place, we would also benefit from more \
beta releases over a slightly longer period. They would be packaged into the beta and \
RC releases of those distributions thus enabling more pre-release testing.<br><br>All \
of this would benefit both upstream and downstream:<br><br>   - More pre-release and \
just released software testing as users test the new distribution version directly \
with the KDE beta and fresh stable releases<br>   - More updated and happy users \
using the latest release<br>   - Less bugs reported against older releases, more bugs \
reported before the final stable releases<br><br>What do you \
think?<br><br>Thanks!<br><br>Timothée Ravier for the Fedora KDE SIG<br \
clear="all"><div><br></div><div>--  <br></div><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><p \
style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px"><span>Timothée</span> \
<span>Ravier</span><span \
style="text-transform:uppercase;color:rgb(170,170,170);margin:0px"></span></p><p \
style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px"><span>Red \
Hat &amp; Fedora CoreOS Engineer</span></p><p \
style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px 0px \
4px;font-size:12px"><a href="https://www.redhat.com/" \
style="color:rgb(0,136,206);margin:0px" target="_blank">Red \
Hat<span></span></a></p><div \
style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-bottom:4px"></div><p \
style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px;font-size:12px"><span \
style="margin:0px;padding:0px"><a href="mailto:travier@redhat.com" \
style="color:rgb(0,0,0);margin:0px" target="_blank">travier@redhat.com</a>     \
</span>  <span>IM:  <span>travier</span></span></p><div \
style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-top:12px"><table \
border="0"><tbody><tr><td width="100px"><a href="https://www.redhat.com/" \
target="_blank"><img \
src="https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png" \
width="90" height="auto"></a></td></tr></tbody></table></div><table \
border="0"><tbody><tr></tr></tbody></table></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]