kde.org

Adanisi, to linux in KDE 6 Megarelease - Release Candidate 1
@Adanisi@lemmy.zip avatar

I can’t wait to try this out!

flying_sheep,
@flying_sheep@lemmy.ml avatar

Well then do it! There’s probably VM images around with a working installation

rysiek, (edited ) to linux in KDE 6 Megarelease - Release Candidate 1
@rysiek@szmer.info avatar

Will we get tabbed/grouped windows finally again? Been waiting for this for half more than a decade.

pathief, to linux in KDE 6 Megarelease - Release Candidate 1
@pathief@lemmy.world avatar

Any exciting features coming up with plasma 6?

domi,
@domi@lemmy.secnd.me avatar

HDR support is the feature I’m mostly looking forward to.

aniki, to linux in KDE 6 Megarelease - Release Candidate 1

I never understood the Wayland hate until I tried to get it working with KDE Plasma on a Orange Pi.

troyunrau, to linux in KDE 6 Megarelease - Release Candidate 1
@troyunrau@lemmy.ca avatar

Not sure if it’s still the same as it was back in my day, but KDE’s “release candidate” nomenclature was always a bit of a misnomer. You’d never see RC1 actually released as final. What it really means is that the alpha “feature refinement” beta “bug fixing” phase is over, and it’s the final testing phase for showstoppers. However, the definition of showstopper seemed always to be very wide. Thus, a lot of bugs still get reported and fixed during this phase, and RC really means “beta, but towards the end of the pipeline”.

Which is in contrast to the Linux kernel where a RC can be declared ship-ready and simply get renamed.

Admittedly there’s a fairly large impact difference between kernel level bugs, and say a bug in Okular…

simple,

The nomenclature is actually correct here, and a lot of other software use it, at least from everything I’ve seen. Release candidate means it’s stable and (usually) feature complete but could have bugs and needs testing before they launch it.

Prototype --> Alpha --> Beta --> Release Candidate --> Release

Oisteink,

It’s still a misuse of the word - if your software needs testing it’s not a candidate you would release unless you’re a multi-billion gaming company or Cisco

FooBarrington,

Wiktionary: (software engineering) A version of a program that is nearly ready for release but may still have a few bugs; the status between beta version and release version.

Oxford: a version of a product, especially computer software, that is fully developed and nearly ready to be made available to the public. It comes after the beta version.

I couldn’t find more definitions from “big” dictionaries, but literally no definition I’ve seen agrees with you. I wonder why that is.

troyunrau,
@troyunrau@lemmy.ca avatar

If you’re as old as I am, you’ll recall software using the term “gamma” release instead of “release candidate” for that phase. ;)

hersh,

This is correct, albeit not universal.

KDE has a predefined schedule for “release candidates”, which includes RC2 later this month. So “RC1” is clearly not going to be the final version. See: community.kde.org/…/February_2024_MegaRelease

This is at least somewhat common. In fact, it’s the same way the Linux kernel development cycle works. They have 7 release candidates, released on a weekly basis between the beta period and final release. See: www.kernel.org/category/releases.html

In the world of proprietary corporate software, I more often see release candidates presented as potentially final; i.e. literal candidates for release. The idea of scheduling multiple RCs in advance doesn’t make sense in that context, since each one is intended to be the last (with fingers crossed).

It’s kind of splitting hairs, honestly, and I suspect this distinction has more to do with the transparency of open-source projects than anything else. Apple, for example, may indeed have a schedule for multiple macOS RCs right from the start and simply choose not to share that information. They present every “release candidate” as being potentially the final version (and indeed, the final version will be the same build as the final RC), but in practice there’s always more than one. Also, Apple is hardly an ideal example to follow, since they’ve apparently never even heard of semantic version numbering. Major compatibility-breaking changes are often introduced in minor point releases. It’s infuriating. But I digress.

Lettuceeatlettuce, to linux in KDE 6 Megarelease - Release Candidate 1
@Lettuceeatlettuce@lemmy.ml avatar

Planning on testing for bugs, I’m super excited for this release!

Hopefully it will fix the few remaining Wayland bugs I’ve been experiencing and I can move 100% onto Wayland when Nobara upgrades to plasma 6.

Mikesomething, to linux in KDE Plasma 5.27.10, Bugfix Release for December

Praying they bring back different backgrounds for different desktops. 🤞🤞

interceder270, to linux in KDE Plasma 5.27.10, Bugfix Release for December

Not really looking forward to KDE6.

KDE5 is great and does everything I need it to. I feel like upgrading is just going to introduce issues while bringing nothing new to the table.

The only thing I would like to change are bigger scrollbars or have the ability to easily resize them. Something tells me this isn’t going to be included in KDE6, though.

TheGrandNagus,

Don’t upgrade then.

I for one am looking forward to it. They seem to be fixing a lot of issues that I currently have with Plasma that prevents me from using it.

interceder270,

I’m on Manjaro, so I think it’ll be included shortly after it’s released :(

TheGrandNagus,

Sounds like a good thing to me.

Grangle1, to linux in KDE Plasma 5.27.10, Bugfix Release for December

On Neon in Wayland it moved the application launcher and notifications to the center of the screen. I saw an issue opened for it just now, so hopefully it will be fixed soon. But I’m expecting it will likely just be a thing until Plasma 6 because that is likely where 100% of their resources are right now.

Pantherina, (edited )

Try to recreate the panel?

And yes, Plasma6 is usable now, it seems like everything is just working and I am close to rebasing. There is a Fedora Kinoite variant which is in my experience way better than Neon Unstable

const_void,

Except for the fact that several major programs (dolphin) crash on a regular basis. It’s definitely not ready for the average yet.

Strit,
@Strit@lemmy.linuxuserspace.show avatar

Did not happen to me when I updated on Arch. So might be a Neon quirk.

be_excellent_to_each_other, to linux in KDE Plasma 6 Megarelease - Beta 1
@be_excellent_to_each_other@kbin.social avatar

I started using Plasma 5 a smidge before devs were saying it was ready for primetime. That was my conversion from Gnome (which I was very happy to leave by then) and it's been nothing but positive.

I will wait for the full release of Plasma 6, but I'm super excited for it. I still <3 Plasma 5.

Thank you KDE devs!

dino, to linux in KDE Plasma 6 Megarelease - Beta 1

Maybe windows rules will now work properly instead of being buggy and delete themselves…fingers crossed Imho KDE is too big, there are so many cogwheels they miss the opportunity to actually polish each and every aspect.

e.g. why does KDE need a specific videoplayer?

JRepin, to linux in KDE Plasma 6 Megarelease - Beta 1
@JRepin@lemmy.ml avatar

Running surprisingly well for a beta. I really hope to find some free time and help some more with reporting the minor bugs left during the end of the year vacation time and help polish for the final release.

jameskirk, to linux in KDE Plasma 6 Megarelease - Beta 1
@jameskirk@startrek.website avatar

To a “newbie”, what does this mean? I transitioned to Linux full time less than a year ago and settled with KDE. Will this affect me in any way?

TJmCAwesome, to linux in KDE Plasma 6 Megarelease - Beta 1

Will this affect SteamOS in any way? I guess the development on that is separate from KDE but I don’t really know.

CaptDust, to linux in KDE Plasma 6 Megarelease - Beta 1

C U B E

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #