Re: Draft for Plasma 6.6 schedule
It would be very much preferred if Plasma 6.7 Qt requirement remained at 6.10, as this would allow backporting to the upcoming Kubuntu 26.04 LTS. Thanks.
Re: Draft for Plasma 6.6 schedule
>It would be very much preferred if Plasma 6.7 Qt requirement remained at 6.10 We should be able to do that. I can't think of any new API from Qt 6.11 we want, and it would be a bit of a rush anyway. David
Re: Draft for Plasma 6.6 schedule
On Mon, Dec 15, 2025 at 9:14 AM Martin Riethmayer wrote: > > Hi everyone, > > with the holiday season coming up, I'd like to propose a schedule for > Plasma 6.7 before that. > > Plasma 6.7 might be a bit special, as it's the last version with X11 > support [3], and there was the question raised, if some extra bug-fix > releases should be scheduled for 6.7, i.e. making 6.7 the first LTS > release for Plasmas 6.X series? This has moved a bit. The plan as we left it on the last 2 meetings was 6.7 would get support until 6.9 branches, sticking with the usual 4 month schedule. We don't want to do LTS's or use that phrase anywhere. It implies something we don't want to imply. Assuming 6.9 is exactly 1 year after this 6.6, that puts the last 6.7 release possible as being 12th Jan 2027. David
Re: Draft for Plasma 6.6 schedule
On Mon, Dec 15, 2025 at 10:14 PM Martin Riethmayer
wrote:
> Hi everyone,
>
Hi Martin,
>
> with the holiday season coming up, I'd like to propose a schedule for
> Plasma 6.7 before that.
>
> Plasma 6.7 might be a bit special, as it's the last version with X11
> support [3], and there was the question raised, if some extra bug-fix
> releases should be scheduled for 6.7, i.e. making 6.7 the first LTS
> release for Plasmas 6.X series?
>
> This could be a possible schedule with 2 additional bugfix releases:
>
> 6.6.80 2026-04-23 (repo and soft feature freeze)
> 6.6.90 Beta 1 2026-05-07
> 6.6.91 Beta 2 2026-05-21
> 6.7.0 TAR 2026-06-04
> 6.7.0 Release 2026-06-09
> 6.7.1 2026-06-16
> 6.7.2 2026-06-23
> 6.7.3 2026-07-07
> 6.7.4 2026-07-28
> 6.7.5 2026-09-01
> 6.7.6 2026-10-27
> 6.7.7 2027-01-26
> 6.7.8 2027-06-22
>
This sort of implies that we will have functional CI for the entire way
through to 6.7.8, which is much easier said than done.
A big part of the challenge here is that Plasma tends to require very new
versions of it's dependencies (which is why the CI system as a whole is
based on a rolling release distro). That means 6.7.0 will have to use CI
based on a rolling release image - as no released distro will be able to
meet those requirements - and then at some point subsequent to that the
series will have to transition to a conventional distribution. That will
require developing an additional image and everything else that comes along
with it.
We currently use OpenSUSE Tumbleweed for our Linux CI, however it looks
like Leap 16.1 isn't due out until October 2026, with a freeze around
May-July 2026 (so it's questionable whether Plasma 6.7 will even ship in
Leap 16.1 given that release schedule depending on how flexible the
schedule is). If we can use Leap 16.1 it isn't too bad, otherwise we'd have
to develop an entire CI image build centered around another distribution -
which is substantially more expensive time investment wise.
>
>
> Things to note:
>
> - The schedule is based on the 3-releases-a-year model, thus I aimed for
> 6.7.0 to be about 4 months after 6.6.0 (scheduled for 2026-02-17).
> It's also based on the release of the "best matching" frameworks
> release, which influences the date of Beta 1 (i.e. Beta 1 "will usually
> happen on Thursday following the corresponding KDE Frameworks release"
> [1] ), which could in turn make 6.7 depend on FW 6.26. Those two kind of
> influence each other.
>
> - Required Qt version could remain at Qt 6.10, or could probably use Qt
> 6.11 which is currently scheduled to be released in March 2026[2].
>
> - I have not taken into consideration any release schedules of
> distributions
>
Given this is essentially planned to be an LTS release (given the support
out to mid-2027) that is quite relevant here I'd say.
>
> - The Blog post "Goig all-in on a Wayland future" [3] says "The Plasma
> X11 session will be supported by KDE into early 2027", which kind of
> implies at least one extra release (6.7.7). I've added another one
> (6.7.8) by Fibonacci-sequence (i.e. 21 weeks after 6.7.7) in my
> proposal, but this is just for showing the date. I'm not aware of any
> formal decision how many extra bug-fix releases will be made, so this is
> up for discussion if it should be reduced to less or extended to even
> more bug-fix releases. Also, it might be worth discussing if it's good
> to put an official "LTS" label on it, or to give an assurance like for
> Plasma 5.27 ("In case of urgent bugfixes or security issues, another
> release might be made")[4].
>
> Let me know your thoughts on this, I'm happy to adjust the schedule or
> (if no objections come) to put it on the wiki and the phabricator calendar.
>
> Best regards
>
> Martin
>
Thanks,
Ben
>
>
> [1] https://community.kde.org/Schedules/Plasma_6#Beta
> [2] https://wiki.qt.io/QtReleasing
> [3] https://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/
> [4] https://community.kde.org/Schedules/Plasma_5#Future_releases
>
Re: Draft for Plasma 6.6 schedule
On 29/9/25 22:48, Martin Riethmayer wrote: Hi everyone, as discussed on Matrix (plasma-devel), I've drafted a release schedule for the Plasma 6.6 release: - Required Qt version could be Qt 6.10, as that is supposed to be releases in early October. CI has to be updated in time and admins have to be notified about this if Qt 6.10 is chosen over 6.9. Qt 6.11 is currently scheduled to be released in March 2026, so isn't an option[2]. In this regard, "Qt Next" is already available as a CI target in GitLab. I would suggest all of Plasma and Frameworks be set up with this if it is not already, that way it is all tested against 6.9 and 6.10 no matter which ends up being the goal. Simply add "- /gitlab-templates/linux-qt6-next.yml" to the gitlab-ci.yml file in the repos. Example in Kate at https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_type=heads#L8 Justin
Re: Draft for Plasma 6.6 schedule
On Monday, 6 October 2025 14:43:42 IST you wrote: > Hi Bhushan, > > sure, I can pre-pone or post-pone any date. > > I'm wondering, though, if it would make more sense to post-pone the > entire schedule by 1 week? > > That would result in: > > 6.5.80repo and soft feature freeze2026-01-08 > 6.5.906.6 Beta 1 2026-01-22 > 6.5.916.6 Beta 2 2026-02-05 > TAR 2026-02-19 > 6.6.0 2026-02-24 > 6.6.1 2026-03-03 > 6.6.2 2026-03-10 > 6.6.3 2026-03-24 > 6.6.4 2026-04-14 > 6.6.5 2026-05-19 > 6.6.6 2026-07-14 > > That would solve Jan 1st, your holiday on Jan 14th/15th, FOSDEM. It solves 2 issue but not FOSDEM. I am stying in Brussels after FOSDEM for postmarrketOS hackathon. So new date would be travel date. And given it introduces other conflicts. I think just moving beta on Tuesdays is fine :) signature.asc Description: This is a digitally signed message part.
Re: Draft for Plasma 6.6 schedule
On Mon, Sep 29, 2025 at 2:19 PM Martin Riethmayer wrote: > > Hi everyone, > > as discussed on Matrix (plasma-devel), I've drafted a release schedule > for the Plasma 6.6 release: > > 6.5.80 repo and feature freeze 2026-01-01 > 6.5.90 6.6 Beta 1 2026-01-15 > 6.5.91 6.6 Beta 2 2026-01-29 > TAR 2026-02-12 > 6.6.0 2026-02-17 > 6.6.1 2026-02-24 > 6.6.2 2026-03-03 > 6.6.3 2026-03-17 > 6.6.4 2026-04-07 > 6.6.5 2026-05-12 > 6.6.6 2026-07-07 Lets make sure we use the phrase "soft feature freeze" and the hard freeze is on beta 1. Feature freeze over Christmas is going to be annoying, but I don't think there's much other option to keep the rough schedule and align with frameworks. Fortunately there's not too much work to do on soft feature freeze day itself. +1. Thanks for taking care of this. David
Re: Draft for Plasma 6.6 schedule
Hi Martin, I want to adjust schedule for at least Beta dates little bit maybe. On Monday, 29 September 2025 18:48:50 IST Martin Riethmayer wrote: > Hi everyone, > > as discussed on Matrix (plasma-devel), I've drafted a release schedule > for the Plasma 6.6 release: > > 6.5.80repo and feature freeze 2026-01-01 I am thinking people might miss merging important features because of holidays, It is soft feature freeze anyway and we will have some time. But still, worth mentioning. > 6.5.906.6 Beta 1 2026-01-15 I am on holiday for 14 and 15th January, so can not do necessary release process. However we can move it to Tuesday this time around. That is doable for me. > 6.5.916.6 Beta 2 2026-01-29 On this date, I am travelling for FOSDEM and another hackathon later on. So this also we can maybe pre-pone this to also Tuesday instead? Thanks. signature.asc Description: This is a digitally signed message part.
