Hi,
Jonathan announced that he will step back from doing Plasma releases.
This means for 6.4 and forward we need someone else to do releases
or multiple persons that share the work (didn't quite work out for frameworks).
David
Hi,
the tarball for kwin 6.3.3 contains a wrong version number in its CMake
files, causing build failures in dependent projects.
There's a new 6.3.3.1 tar to fix that. Alternatively apply the attached
patch:
-set(PROJECT_VERSION "6.3.2") # Handled by release scripts
+set(PROJECT
k (didn't quite work out for
> frameworks).
>
> David
Hello David,
Please keep us (Promo) in the loop as to who we have to interface with to
coordinate release, announcement and promotion on social media.
Cheers
Paul
--
Promotion & Communication
www: https://kde.org
Ma
On Sat, Jan 18, 2025 at 12:59 AM Carl Schwan wrote:
> On Thu, Dec 5, 2024, at 4:53 PM, Noah Davis wrote:
> > Hello everyone, I would like to propose moving Spectacle to the Plasma
> > development release schedule. It already depends heavily on Plasma for
> > its core functio
On Thu, Dec 5, 2024, at 4:53 PM, Noah Davis wrote:
> Hello everyone, I would like to propose moving Spectacle to the Plasma
> development release schedule. It already depends heavily on Plasma for
> its core functionality. When a Plasma bug or feature happens on a new
> release
Gear future releases (not 24.12.x obviously)
Cheers,
Albert
>
> On Thu, Dec 12, 2024 at 1:41 PM Noah Davis wrote:
> > Thinking about it again, I don't think it would actually be necessary
> > to make 24.12 a short release. I could easily handle 24.12.1-24.12.3
> > a
No, in a previous email on this thread, I decided it actually wouldn't
be very difficult to maintain 24.12 and 6.3 at the same time.
On Thu, Dec 12, 2024 at 1:41 PM Noah Davis wrote:
> Thinking about it again, I don't think it would actually be necessary
> to make 24.12 a short
El diumenge, 15 de desembre del 2024, a les 10:43:39 (Hora estàndard del
Centre d’Europa), Jonathan Riddell va escriure:
> I have added Spectacle to the Plasma 6.3 release list
> https://invent.kde.org/sdk/releaseme/-/commit/82f6d5cf68d5c5942bbcdd9f7209f8
> 7f305b1824
Having a look at t
I have added Spectacle to the Plasma 6.3 release list
https://invent.kde.org/sdk/releaseme/-/commit/82f6d5cf68d5c5942bbcdd9f7209f87f305b1824
However tracking translations from trunk for the Plasma branch will need
some pondering where to set that.
To set the version number to the Plasma format
Thanks, done.
On Sat, Dec 14, 2024 at 6:09 PM Albert Astals Cid wrote:
>
> El dissabte, 14 de desembre del 2024, a les 22:19:04 (Hora estàndard del
> Centre d’Europa), Noah Davis va escriure:
> > Ok, back to a full 24.12 release cycle with a Plasma 6.3 release as
> > well.
El dissabte, 14 de desembre del 2024, a les 22:19:04 (Hora estàndard del
Centre d’Europa), Noah Davis va escriure:
> Ok, back to a full 24.12 release cycle with a Plasma 6.3 release as
> well. Jonathan, can you add Spectacle to the Plasma 6.3 release
> schedule? Once you've don
Ok, back to a full 24.12 release cycle with a Plasma 6.3 release as
well. Jonathan, can you add Spectacle to the Plasma 6.3 release
schedule? Once you've done that, I will notify the distributions
mailing list and change the version numbers in the repository. I will
also set an event
Albert Astals Cid ha scritto:
> El dijous, 12 de desembre del 2024, a les 19:48:20 (Hora estàndard del Centre
> d’Europa), Luigi Toscano va escriure:
>> Noah Davis ha scritto:
>>> Thinking about it again, I don't think it would actually be necessary
>>> to
El dijous, 12 de desembre del 2024, a les 19:48:20 (Hora estàndard del Centre
d’Europa), Luigi Toscano va escriure:
> Noah Davis ha scritto:
> > Thinking about it again, I don't think it would actually be necessary
> > to make 24.12 a short release. I could easily handle 24.
between feature releases and that is manageable by everyone affected
by the change.
On Thu, Dec 12, 2024 at 1:48 PM Luigi Toscano wrote:
>
> Noah Davis ha scritto:
> > Thinking about it again, I don't think it would actually be necessary
> > to make 24.12 a short release. I could
Thinking about it again, I don't think it would actually be necessary
to make 24.12 a short release. I could easily handle 24.12.1-24.12.3
and 6.2.90-6.3.3 simultaneously. It's not like any big changes will
make it into 24.12 at this point. Spectacle 6.3 will probably get more
love
Noah Davis ha scritto:
> Thinking about it again, I don't think it would actually be necessary
> to make 24.12 a short release. I could easily handle 24.12.1-24.12.3
> and 6.2.90-6.3.3 simultaneously. It's not like any big changes will
> make it into 24.12 at this poi
On 6/12/24 02:23, Noah Davis wrote:
Hello everyone, I would like to propose moving Spectacle to the Plasma
development release schedule. It already depends heavily on Plasma for
its core functionality. When a Plasma bug or feature happens on a new
release that affects Spectacle, Spectacle can&#
We can do standalone releases of it no problem.
Jonathan
ly risky changes in Spectacle between now and the 6.3
> beta release (2025-01-09).
We will get lots of complaints that a tarball is missing if we stop releasing
one of the hundreds of tarballs we release with KDE Gear at a "random" cutoff
point, so I would really prefer not to do t
hich version of Plasma we target since Plasma releases are
offset from Gear releases by 2 months. I also don't think there will
be any particularly risky changes in Spectacle between now and the 6.3
beta release (2025-01-09).
On Wed, Dec 11, 2024 at 3:12 AM David Redondo wrote:
>
> Am M
El dimecres, 11 de desembre del 2024, a les 9:11:37 (Hora estàndard del Centre
d’Europa), David Redondo va escriure:
> Am Mittwoch, 11. Dezember 2024, 01:24 schrieb Noah Davis:
> > Plasma 6.3, which should be branched by 2025-01-09
>
> Wouldn't 6.4 make more sense? As in move it to Plasma after 6
On Wed, Dec 11, 2024 at 9:56 PM Jonathan Riddell wrote:
> It's not a sysadmin task, it's a release team task, remind Albert to
> remove it from the kde gear list at the appropriate time then remind me to
> add it to the Plasma list.
>
> The sysadmin task would be to
It's not a sysadmin task, it's a release team task, remind Albert to remove
it from the kde gear list at the appropriate time then remind me to add it
to the Plasma list.
The sysadmin task would be to move it from the graphics invent category to
the plasma invent category so you can as
On Wednesday, 11 December 2024 01.24.37 Central European Standard Time Noah
Davis wrote:
> Plasma 6.3, which should be branched by 2025-01-09
>
I think too that targeting 6.4 is safer and more practical at this point
--
Marco Martin
Am Mittwoch, 11. Dezember 2024, 01:24 schrieb Noah Davis:
> Plasma 6.3, which should be branched by 2025-01-09
>
Wouldn't 6.4 make more sense? As in move it to Plasma after 6.3 is done.
Otherwise there will be two releases practically be one after another and you
have to
maintain two stable bra
Plasma 6.3, which should be branched by 2025-01-09
On Tue, Dec 10, 2024 at 5:46 PM Albert Astals Cid wrote:
>
> El diumenge, 8 de desembre del 2024, a les 21:33:21 (Hora estàndard del Centre
> d’Europa), Noah Davis va escriure:
> > Of course, I do not suggest changing the relea
El diumenge, 8 de desembre del 2024, a les 21:33:21 (Hora estàndard del Centre
d’Europa), Noah Davis va escriure:
> Of course, I do not suggest changing the release schedule for versions
> that have already been branched. If we wanted to do the switch
> quickly, we could do another re
Of course, I do not suggest changing the release schedule for versions
that have already been branched. If we wanted to do the switch
quickly, we could do another release for Plasma 6.3 (setup before
2024-12-26).
By the way, I am not familiar with the process for changing the
release schedule of
El dijous, 5 de desembre del 2024, a les 16:53:33 (Hora estàndard del Centre
d’Europa), Noah Davis va escriure:
> Hello everyone, I would like to propose moving Spectacle to the Plasma
> development release schedule. It already depends heavily on Plasma for
> its core functionality. When
Hello everyone, I would like to propose moving Spectacle to the Plasma
development release schedule. It already depends heavily on Plasma for
its core functionality. When a Plasma bug or feature happens on a new
release that affects Spectacle, Spectacle can't push anything to users
until the
Nicolas is right there's no dependency on libplasma from Spacebar just my
mistake.
But we discussed it in the Plasma room just now and decided they both
should be released together and since Plasma Dialer depends on Plasmay
things it would be best to release it with Plasma, so I'll inc
On 22.08.24 13:29, Jonathan Riddell wrote:
Plasma Dialer depends on KWin and Plasma Wayland Protocols, Spacebar
(SMS messaging app) similarly depends on libplasma, so it would seem
sensible to have these as part of Plasma releases.
Where does Spacebar depend on libplasma?
Repo freeze is in
Plasma Dialer depends on KWin and Plasma Wayland Protocols, Spacebar (SMS
messaging app) similarly depends on libplasma, so it would seem sensible to
have these as part of Plasma releases.
Repo freeze is in 7 days time on 29th August.
We can ask at the Plasma meeting next Monday.
They're not the
On Thu, Aug 22, 2024 at 10:57 AM Albert Astals Cid wrote:
> El dijous, 15 d’agost del 2024, a les 10:41:53 (CEST), Carl Schwan va
> escriure:
> > Hi,
> >
> > Me again, this time to ask to move Plasma Dialer and Spacebar to the
> Plasma
> > release cycle (or gear
El dijous, 15 d’agost del 2024, a les 10:41:53 (CEST), Carl Schwan va
escriure:
> Hi,
>
> Me again, this time to ask to move Plasma Dialer and Spacebar to the Plasma
> release cycle (or gear release cycle).
>
> I did the two last releases 23.01 and 24.08 for dialer and 23.
Hi,
Me again, this time to ask to move Plasma Dialer and Spacebar to the Plasma
release cycle (or gear release cycle).
I did the two last releases 23.01 and 24.08 for dialer and 23.01 and 24.05 for
spacebar, and as you might guess from the version numbers, the frequency of the
release as been
On Friday, 7 June 2024 21.11.07 CEST Jonathan Riddell wrote:
> The main action happens around September, pic attached. We have repo
> and soft feature freeze 29 August, 6.2 beta 12 september, 6.2 Tars on
> 3 October to be released 8 October. That means 6.1.5 and 6.2 beta
> happen during Akademy.
>
https://calendar.google.com/calendar/u/0?cid=MDMxZ2tncWcxaGpmOGxjbWowZW0xZDJzajhAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
I've filled in dates on this calendar with the remaining 6.1 release
dates and proposed 6.2 release dates using the normal 4 monthly
release cycle
The main action happens a
Plasma 6.1 tars are due on Thu 13 June and release Tue 18 June. I'm
going to be away on holiday paddling under the midnight sun in Norwary
during this time. Would anyone else like to be release manager?
Jonathan
Hi Dan, can I make a plasma pass release so that it builds with Plasma 6?
Jonathan
Am Mittwoch, 7. Februar 2024, 10:37:13 CET schrieb Kai Uwe Broulik:
> Hi,
>
> plasma-integration already (which I am NOT happy about!) creates a GL
> context to check whether to use software rendering, there we could also
> check the GL_VENDOR and set basic render loop.
>
Yes we did that in 5 a
Hi,
plasma-integration already (which I am NOT happy about!) creates a GL
context to check whether to use software rendering, there we could also
check the GL_VENDOR and set basic render loop.
But backporting won’t hurt either way I’d say.
Cheers
Kai Uwe
Am 07.02.24 um 10:13 schrieb David R
Hi,
when using Wayland on Nvidia there is a significant problem that QtQuick
windows freeze when resized, this can also manifest in plasma popups sometimes
not showing up.
ref. https://bugreports.qt.io/browse/QTBUG-95817
This can be worked around with using the basic render loop instead of the
That's on my todo for today :)
Jonathan
On Mon, 6 Nov 2023 at 21:55, Neal Gompa wrote:
> On Mon, Nov 6, 2023 at 11:21 AM Jonathan Riddell wrote:
> >
> > Diff from 5.27
> > -aura-browser
> > -aura-browser
> > +kactivities
> > +kactivities-stats
> > -khotkeys
> > -krdp
> > +kwayland
> > -plank-
On Mon, Nov 6, 2023 at 11:21 AM Jonathan Riddell wrote:
>
> Diff from 5.27
> -aura-browser
> -aura-browser
> +kactivities
> +kactivities-stats
> -khotkeys
> -krdp
> +kwayland
> -plank-player
> -plank-player
> -plasma-bigscreen
> +plasma-framework
> -plasma-remotecontrollers
> +plasma5support
> +pr
Good point, I've added in kglobalacceld now
Jonathan
On Mon, 6 Nov 2023 at 17:51, Antonio Rojas wrote:
> El lunes, 6 de noviembre de 2023 17:21:06 (CET) Jonathan Riddell escribió:
>
> > Diff from 5.27
>
> Hi,
>
> What about kglobalacceld?
>
>
>
>
>
El lunes, 6 de noviembre de 2023 17:21:06 (CET) Jonathan Riddell escribió:
> Diff from 5.27
Hi,
What about kglobalacceld?
Diff from 5.27
-aura-browser
-aura-browser
+kactivities
+kactivities-stats
-khotkeys
-krdp
+kwayland
-plank-player
-plank-player
-plasma-bigscreen
+plasma-framework
-plasma-remotecontrollers
+plasma5support
+print-manager
+wacomtablet
Complete list:
bluedevil
breeze
breeze-grub
breeze-gtk
breeze-
On Tue, Sep 26, 2023 at 12:29 AM Albert Astals Cid wrote:
>
> El dimarts, 26 de setembre de 2023, a les 0:28:15 (CEST), Albert Astals Cid va
> escriure:
> > https://community.kde.org/Schedules/February_2024_MegaRelease
> >
> > Beta 1 is during Qt World Summit that is not ideal but I guess doable?
al pointers.
> >>
> >> Given no one did seem to oppose so far, I would consider to switch
> >> Kate to Qt
> >> 6 in master next Wednesday and start the bit Qt 6 run :)
> >
> > When you switch a branch to qt6, please remember to ping the
> > tran
ne", "stable": "none", "stable_kf5": "release/23.08",
"trunk_kf5": "master"}
Would it be something like:
{"trunk": "master", "stable": "none", "stable_kf5": "release/23.08",
"trunk_kf5": "none"}
Greetings
Christoph
christ...@cullmann.io ha scritto:
> On 2023-09-05 23:08, Albert Astals Cid wrote:
>> El dimarts, 5 de setembre de 2023, a les 22:42:13 (CEST),
>> christ...@cullmann.io va escriure:
>>> On 2023-09-04 22:59, Albert Astals Cid wrote:
>>> > El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), Davi
update the i18n branch information
Anything else I am missing?
Hi,
Thanks for the additional pointers.
Given no one did seem to oppose so far, I would consider to switch Kate
to Qt 6 in master next Wednesday and start the bit Qt 6 run :)
(If nothing comes up here)
The everybody had a w
https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_type=heads
and require KF 6 + Qt 6 in the CMake files or is there additional stuff
that
needs updates to avoids one breaks stuff?
Greetings
Christoph
- The KDE Gear release will move by 2 months to allow for the extra
time n
dependency info
But this is autogenerated by Nico scripts nowadays so... maybe not? or prod
him to run the script?
projects/*/*/i18n.json
to update the i18n branch information
Anything else I am missing?
Cheers,
Albert
>
> Greetings
> Christoph
>
> >> - The KDE Gea
ill be open for Qt6 code to land for those
> ready to move. Not all apps need to port.
For the trigger happy among us...
This is a plan/proposal, let's give people at least one week to comment/
disagree on it before making master Qt6-only for Gear apps.
>
> - The KDE Gear release w
Following on from the last Akademy we checked where we were with our
development progress in a meeting and settled on the following plan
for all 3 major parts:
- In KDE Gear master will be open for Qt6 code to land for those
ready to move. Not all apps need to port.
- The KDE Gear release will
As a reminder this meeting is tonight in 3 hours.
David
Video call at https://meet.kde.org/b/ada-mi8-aem
Thanks for organizing this, David. Where and how will the meeting be held?
Nate
On 8/22/23 09:22, David Edmundson wrote:
A time has been chosen on the poll with a clear winner:
4th September 18:00 CEST
See you all there
David Edmundson
A time has been chosen on the poll with a clear winner:
4th September 18:00 CEST
See you all there
David Edmundson
As discussed at Akademy we need to finalize the release of KF6 /
Applications with 6 and Plasma 6.
Applications can't release without Plasma (for Breeze + Plasma Integration)
Plasma is weakened without kio-extras
Both depend on Frameworks which needs a final release.
We want to be fairly s
5.27.7 is scheduled for Tuesday August 8th. I'm away on adoption leave and
won't be available that day, the best I can do is say I might be able to
squeeze it in somewhere in the following two weeks. If anyone else wants
to do it let me know and I'll take you through how it's done.
Jonathan
). The former is a regression
introduced in 5.25.5. Instead of hoping distros will apply those
themselves I propose we make a 5.25.5.1 release for plasma-workspace.
Cheers
Nico
. Instead of hoping distros will apply those
themselves I propose we make a 5.25.5.1 release for plasma-workspace.
Cheers
Nico
Sounds good, thanks Jonathan!
Aleix
On Fri, May 6, 2022 at 12:56 PM Jonathan Riddell wrote:
>
> I'm proposing Tuesday July 5 for a 5.24.6LTS release. It's 11 weeks after
> the 5.24.5 release and is mostly timed to be useful to Kubuntu.
>
> Jonathan
>
>
> On
I'm proposing Tuesday July 5 for a 5.24.6LTS release. It's 11 weeks after
the 5.24.5 release and is mostly timed to be useful to Kubuntu.
Jonathan
On Thu, 5 May 2022 at 10:34, Jonathan Riddell wrote:
> Does anyone have a request for a release date for the next or followi
Does anyone have a request for a release date for the next or following
5.24 LTS releases?
I've had one from Kubuntu asking "the .6 is at least a few weeks to a month
before the 22.04.1 point release on August 4"
Any more?
Jonathan
Sensible enough, but the developers do need to follow Plasma's release
schedule then. Changing name after repo freeze shouldn't happen. Nor
should adding new dependencies or depending on versions of Frameworks newer
than our release specifies
https://invent.kde.org/plasma/plasma-mobil
On Tue, Feb 8, 2022 at 3:21 PM Jonathan Riddell wrote:
>
> plasma-phone-components is released as part of Plasma which has an
> established release process that we review at the start of each cycle. This
> time it was renamed after the repo freeze and after the beta
plasma-phone-components is released as part of Plasma which has an
established release process that we review at the start of each cycle.
This time it was renamed after the repo freeze and after the beta which
causes unpredictable problems in the packaging process.
Should plasma-phone-components
a 5.23 during F35 Beta or F35 Final. A big
part of why I was comfortable with switching to Wayland by default[3]
for Fedora Linux 34 was that I was shipping the latest in-development
release at that time. Looking at the schedule now, we're basically
going to have to sit out of Plasma 5.23 lik
We discussed this some more, and we are not in favour of moving
forwards for Fedora:
Reasons given were:
- It either cuts into our beta period, or causes us issues with
framework releases.
- Fedora has regular releases anyway
- It collides with the promo plans above
- .0 releases tend to not be
On Tuesday, 8 June 2021 15:59:37 CEST Nate Graham wrote:
> Hello release folks!
>
> Plasma 5.23 is currently scheduled to be released on 7 October. I've
> been talking with the Fedora packagers about this, and been informed
> that if we bump up the release by one week--shippi
On Tuesday, 8 June 2021 14:59:37 BST Nate Graham wrote:
> Hello release folks!
>
> Plasma 5.23 is currently scheduled to be released on 7 October. I've
> been talking with the Fedora packagers about this, and been informed
> that if we bump up the release by one
Seems a friendly thing to do. We can discuss it during the kickoff session
at akademy.
Jonathan
On Tue, 8 Jun 2021 at 14:59, Nate Graham wrote:
> Hello release folks!
>
> Plasma 5.23 is currently scheduled to be released on 7 October. I've
> been talking with the Fedora pac
Hello release folks!
Plasma 5.23 is currently scheduled to be released on 7 October. I've
been talking with the Fedora packagers about this, and been informed
that if we bump up the release by one week--shipping on 31
September--then they can ship Plasma 5.23 in Fedora 35. Is this
some
eople, and find out which tasks are really blockers for KF 6.0 and which
> are not. In fact several Plasma items are not really blockers for KF6.
>
> In the worst case, the first plasma-frameworks release could be delayed
> until Plasma 6 is closer to be ready. Other frameworks don't
On sabato 17 aprile 2021 16:38:32 CEST Friedrich W. H. Kossebau wrote:
> It seems these days the only real user of plasma-frameworks & krunner
> libraries is the Plasma shell itself, with other applications only providing
> plugins/extensions and only targeting Plasma again. IIRC Amarok was the
> o
> It seems these days the only real user of plasma-frameworks & krunner
> libraries is the Plasma shell itself, with other applications only providing
> plugins/extensions and only targeting Plasma again.
That is mostly in line with other discussions in plasma. There is a
ticket splitting plasma-f
Hi,
sorry to bring this up again, but I would be in favor of a switching to 2
releases every year. I'd like to add some reasons to do that on the
promotional side:
1) In Promo, we are quite stepping up our game in the quality of
announcements, to both the website and the release video. W
me in the quality of
> announcements, to both the website and the release video. We are already a
> bit stretched out with time, and having more of that to prepare each release
> would benefit us, especially if we intend - and I think we do - to improve
> our work even further.
I don
ality of announcements,
to both the website and the release video. We are already a bit stretched out
with time, and having more of that to prepare each release would benefit us,
especially if we intend - and I think we do - to improve our work even further.
2)
We have measured that doing
Hi,
sorry to bring this up again, but I would be in favor of a switching to 2
releases every year. I'd like to add some reasons to do that on the promotional
side:
1) In Promo, we are quite stepping up our game in the quality of
announcements, to both the website and the re
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
We discussed this in the Plasma meeting on Monday and I'm afraid there's
little appetite in moving to a 6 monthly release or a 3 monthly release.
We did used to have a 3 monthly schedule but that is too tight given the
length of beta and freezes we want to have now. But also 6 monthly
On Thu, Nov 26, 2020 at 10:38 PM Neal Gompa wrote:
>
> On Thu, Nov 26, 2020 at 10:25 AM Aleix Pol wrote:
> >
> > On Tue, Nov 24, 2020 at 5:10 PM David Edmundson
> > wrote:
> >>>
> >>> As distribution package maintainers, we would like Plasma
On Thu, Nov 26, 2020 at 10:25 AM Aleix Pol wrote:
>
> On Tue, Nov 24, 2020 at 5:10 PM David Edmundson
> wrote:
>>>
>>> As distribution package maintainers, we would like Plasma developers to
>>> slightly alter the release schedule to align releases with a m
On Tue, Nov 24, 2020 at 5:10 PM David Edmundson
wrote:
> 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
>>
>
> 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.
&g
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
niedz., 24 maj 2020 o 20:17 Nate Graham wrote:
> Land it on Plasma/5.19, then manually merge Plasma/5.19 into master,
> same as before.
OK, thank you for confirmation.
--
Regards:
Konrad Materka
Materka wrote:
Hi,
What is the current procedure of merging fixes from release branch
back into master? For example I made a fix for Plasma/5.19 but I want
it in master as well. Merge Request from Plasma/5.19 into master has
conflicts, how to fix them in new GitLab flow?
Sorry if it was discussed
Hi,
What is the current procedure of merging fixes from release branch
back into master? For example I made a fix for Plasma/5.19 but I want
it in master as well. Merge Request from Plasma/5.19 into master has
conflicts, how to fix them in new GitLab flow?
Sorry if it was discussed already, but I
Beta on Thursday so please add features for the announce pronto.
https://share.kde.org/apps/files/?dir=/Community%20Notes/Plasma&fileid=1718757
(sort by modified date, edit Plasma 5.19.md)
or reply here
Jonathan
On vendredi 20 mars 2020 12:16:09 CET David Edmundson wrote:
> >> > Kirigami seems to be rather unstable, I wonder if anything can be done
> >> > to
> >> > improve upon that [*].
> >>
> >> One important thing seems to have been getting sloppy in those repos;
> >> mandatory code reviews.
> >> That'
>> > Kirigami seems to be rather unstable, I wonder if anything can be done to
>> > improve upon that [*].
>
>> One important thing seems to have been getting sloppy in those repos;
>> mandatory code reviews.
>> That's an easy thing to enforce, and we know it makes a huge difference to
>> code.
>>
On 2/18/20 1:37 PM, Albert Astals Cid wrote:
I still don't see why this is a problem, as said Plasma depends on a myriad of
libraries that are building each with their own release model, most probably
with no bugfix releases at all either.
The "we don't control the whole stack
or an LTS Frameworks release to
accompany the Plasma LTS release: to better support our non-Neon
downstreams who want to freeze on the Plasma LTS releases. Right now
we're pushing the job of backporting bugfixes to Frameworks onto them,
rather than making it easy by just giving them tarb
1 - 100 of 609 matches
Mail list logo
