Re: print-manager and wacomtablet to Plasma
On 11/2/23 17:39, Albert Astals Cid wrote: It's true that print-manager is mainly a plasmoid/kded/kcm so if Plasma folks want to adopt it, I'm not against it, please propose a MR like https://invent.kde.org/sysadmin/release-tools/-/merge_requests/39/diffs (but in reverse) Done, see https://invent.kde.org/sysadmin/release-tools/-/merge_requests/41. Having such software follow the Plasma release schedule prevents the problem of unsynchronized changes due to differing release schedules, which bit us multiple times during the Plasma 5 cycle. That's not a good reason, Plasma developers need to remember that there's third party applications out there that may also want to tightly integrate with Plasma, so any breaking change that may affect print-manager or whatever other non-shipped-by-Plasma software should not be happening. For the record, the problem was not breaking changes; we always avoided intentionally making breaking changes due to the existence of 3rd-party widgets and KCMs etc. Rather the issue was unsynchronized UI changes; for example Plasma would introduce a new UI feature or convention and then everything on the Plasma release schedule would opt into it in time for the next release, but software like print-manager not on the Plasma release schedule couldn't sync up until their next release, causing random things to use the old style for a few weeks or months. Not the end of the world of course, but not the kind of seamless UX we were aiming for. Nate
Re: print-manager and wacomtablet to Plasma
El dimecres, 1 de novembre de 2023, a les 1:10:55 (CET), Nate Graham va escriure: > On 10/31/23 17:28, Nicolas Fella wrote: > > On 10/31/23 23:23, Albert Astals Cid wrote: > >> El dimarts, 31 d’octubre de 2023, a les 20:43:47 (CET), Jonathan > >> Riddell va > >> > >> escriure: > >>> As discuccsed in Plasma meeting and just now with KDE gear release > >>> spods, > >>> Plasma would like to take over releases of print-manager and > >>> wacomtablet. > >>> This means renumbering the tars from e.g. 23.08 to 5.80.0. > >>> > >>> Any issues? > >> > >> What's the rationale for such move? > > > > See https://mail.kde.org/pipermail/release-team/2023-June/013081.html > > where I originally brought up the topic > > > > partly it's not relevant any more since we settled on releasing Plasma > > and Gear together this time. The point about these being effectively > > tied to Plasma still stands, and as such releasing them together makes > > sense, for example because it makes it easier to deal with changes in > > their interaction with Plasma > > Yes, the idea is to move into Plasma the things that really only make > sense to use *in* Plasma. It's true that print-manager is mainly a plasmoid/kded/kcm so if Plasma folks want to adopt it, I'm not against it, please propose a MR like https://invent.kde.org/sysadmin/release-tools/-/merge_requests/39/diffs (but in reverse) > Having such software follow the Plasma release > schedule prevents the problem of unsynchronized changes due to differing > release schedules, which bit us multiple times during the Plasma 5 cycle. That's not a good reason, Plasma developers need to remember that there's third party applications out there that may also want to tightly integrate with Plasma, so any breaking change that may affect print-manager or whatever other non-shipped-by-Plasma software should not be happening. Cheers, Albert > > Nate
Re: print-manager and wacomtablet to Plasma
> On Wed, Nov 1, 2023 at 8:44 AM Jonathan Riddell wrote: > > As discuccsed in Plasma meeting and just now with KDE gear release spods, > > Plasma would like to take over releases of print-manager and wacomtablet. > > This means renumbering the tars from e.g. 23.08 to 5.80.0. > > Isn't this going to cause distributions all sorts of pain as package > managers are going to assume 23.08 > 5.80 and refuse to update? It differs from distro to distro of course, but can be worked around. For example in Arch Linux, they have an "epoch" variable they can set in a PKGBUILD to tell Pacman to consider 5.80 (with an epoch of 1) is newer than 23.08 (with an epoch of 0, the default). I'm hoping other distributions/ package managers have thought about this before Thanks, Josh
Re: print-manager and wacomtablet to Plasma
On Wed, Nov 1, 2023 at 8:44 AM Jonathan Riddell wrote: > As discuccsed in Plasma meeting and just now with KDE gear release spods, > Plasma would like to take over releases of print-manager and wacomtablet. > This means renumbering the tars from e.g. 23.08 to 5.80.0. > Isn't this going to cause distributions all sorts of pain as package managers are going to assume 23.08 > 5.80 and refuse to update? > > Any issues? > > Jonathan > > Cheers, Ben
Re: print-manager and wacomtablet to Plasma
On 10/31/23 17:28, Nicolas Fella wrote: On 10/31/23 23:23, Albert Astals Cid wrote: El dimarts, 31 d’octubre de 2023, a les 20:43:47 (CET), Jonathan Riddell va escriure: As discuccsed in Plasma meeting and just now with KDE gear release spods, Plasma would like to take over releases of print-manager and wacomtablet. This means renumbering the tars from e.g. 23.08 to 5.80.0. Any issues? What's the rationale for such move? See https://mail.kde.org/pipermail/release-team/2023-June/013081.html where I originally brought up the topic partly it's not relevant any more since we settled on releasing Plasma and Gear together this time. The point about these being effectively tied to Plasma still stands, and as such releasing them together makes sense, for example because it makes it easier to deal with changes in their interaction with Plasma Yes, the idea is to move into Plasma the things that really only make sense to use *in* Plasma. Having such software follow the Plasma release schedule prevents the problem of unsynchronized changes due to differing release schedules, which bit us multiple times during the Plasma 5 cycle. Nate
Re: print-manager and wacomtablet to Plasma
On 11/1/23 00:28, Nicolas Fella wrote: On 10/31/23 23:23, Albert Astals Cid wrote: El dimarts, 31 d’octubre de 2023, a les 20:43:47 (CET), Jonathan Riddell va escriure: As discuccsed in Plasma meeting and just now with KDE gear release spods, Plasma would like to take over releases of print-manager and wacomtablet. This means renumbering the tars from e.g. 23.08 to 5.80.0. Any issues? What's the rationale for such move? See https://mail.kde.org/pipermail/release-team/2023-June/013081.html where I originally brought up the topic partly it's not relevant any more since we settled on releasing Plasma and Gear together this time. The point about these being effectively tied to Plasma still stands, and as such releasing them together makes sense, for example because it makes it easier to deal with changes in their interaction with Plasma Also, wacomtablet isn't actually part of Gear, it's independently released and there hasn't been a release in a while. By moving it to Plasma we would make sure it does get regular releases
Re: print-manager and wacomtablet to Plasma
On 10/31/23 23:23, Albert Astals Cid wrote: El dimarts, 31 d’octubre de 2023, a les 20:43:47 (CET), Jonathan Riddell va escriure: As discuccsed in Plasma meeting and just now with KDE gear release spods, Plasma would like to take over releases of print-manager and wacomtablet. This means renumbering the tars from e.g. 23.08 to 5.80.0. Any issues? What's the rationale for such move? See https://mail.kde.org/pipermail/release-team/2023-June/013081.html where I originally brought up the topic partly it's not relevant any more since we settled on releasing Plasma and Gear together this time. The point about these being effectively tied to Plasma still stands, and as such releasing them together makes sense, for example because it makes it easier to deal with changes in their interaction with Plasma
Re: print-manager and wacomtablet to Plasma
El dimarts, 31 d’octubre de 2023, a les 20:43:47 (CET), Jonathan Riddell va escriure: > As discuccsed in Plasma meeting and just now with KDE gear release spods, > Plasma would like to take over releases of print-manager and wacomtablet. > This means renumbering the tars from e.g. 23.08 to 5.80.0. > > Any issues? What's the rationale for such move? Cheers, Albert > > Jonathan
