Replies: 3 comments 4 replies
-
On further consideration, this should be in Discussions. Moving. |
Beta Was this translation helpful? Give feedback.
-
We are keeping branches for older shell versions. I released patch versions for multiple older shell versions for a memory leak a while back and then a distro package ook the largest number "latest" release that was the oldest gsconnect for the oldest shell. It was a whole season of very unnecessary bug reports. That said, I think we still should backport fixes to old releases in the future as well when the bug being fixed is major enough. Should probably order the releases in another order and be clearer in the release notes in the hopes that it helps anything. I don't want to have a single code base claiming support for many versions, as then I'd have to test with all of those versions for each release. |
Beta Was this translation helpful? Give feedback.
-
I'd generally agree with Daniel. The two factors here are really time and testing. Personally, I just don't have time to run multiple versions of GNOME on multiple distributions (and distro does make a difference here too). Supporting multiple versions in the same release is not a fun game to play, I can tell you that. The only reasonable way is to keep separate branches, in my experience. Ideally, we could just branch before a new GNOME release and if it's actually used someone will be running it and backporting or requesting backports. I guess my opinion is still generally: if someone wants to do the work, it's fine by me 🤷 |
Beta Was this translation helpful? Give feedback.
-
Describe your request
I get the theory behind only supporting the latest version, but I'm not sure I get the practice.
For example, currently we "only support GNOME 44". Except, there are no distros out there running GNOME 44 yet. Or at least, there weren't when we made the move to GNOME 44. Fedora 38 is still a couple of weeks from release, even now. If Ubuntu 23.4 is out, it's only recently released. But we've been GNOME 44-only since #1577 was merged on March 13, when there were definitely no distros supporting GNOME 44.
And most of the backwards-incompatible changes aren't necessary. Like, the one that broke GNOME 43 compatibility was this change in the QuickMenuToggle
_init
:But here's the thing:
label
is deprecated in that function, but it's not broken. If we'd left it usinglabel
instead, the extension would still be GNOME 43 compatible, and work under GNOME 44. Why are we deliberately breaking things for users?Proposed solution
Don't deliberately (and unnecessarily) break things for users?
IOW, keep compatibility where possible, even if it means staying with deprecated (but still fully functional) API on the latest-and-greatest version for now. We can always create Projects reminders to update things down the road.
Alternatives
For users of GNOME 43 distros? Not many.
GSConnect version
55
Installed from
GitHub releases (zip file)
GNOME Shell version
Any version before 44
Linux distribution/release
Basically all, at the time #1577 was merged
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions