Today I have something very exciting to share: the Alpha release of KDE Linux, KDE’s new operating system! Many of you may be familiar with KDE Linux already through Harald Sitter’s 202…
I’m assuming that’s a genuine question… Normally when people develop a feature they do it once and then it’s “done” and any changes to that feature have to go through the whole feature request -> it’s low priority -> wait 10 years cycle before they actually happen.
Essentially, you have to do it right first time or it might never be fixed.
Just to note, I disagree entirely. Even in commercial development, it’s the core premise of agile development to ship features early and continuously integrate feedback. Granted, lots of companies claim to do agile without actually doing it, but it’s at least not a law of nature what you’re describing.
But with this not being commercial development either way, I really don’t feel like you can make any predictions. If the volunteer that implemented this sees your bug report, they could decide to drop everything else and fix that, because they get to pick their own priorities. They might have the solution in their head right away and it doesn’t take them long at all to implement. Or someone new to the project might decide this sounds like a good issue to get started with.
It’s not a requirement to file a bug report before you comment on anything. Don’t be silly.
It’s not a requirement but if anything is silly it’s acting as if an alpha version is the final release and complaining in a random forum would change anything.
It’s an alpha release.
It’s an alpha release.
You really think they’re going to revisit this? That’s not really how software development works.
I was talking about Flatpak.
Oh my god, be more insufferable.
It’s an alpha release and you’re condemning them to death because of a naming convention.
I reserve my judgement until a final release is made.
How does it work, then? Have you filed a bug report?
I’m assuming that’s a genuine question… Normally when people develop a feature they do it once and then it’s “done” and any changes to that feature have to go through the whole feature request -> it’s low priority -> wait 10 years cycle before they actually happen.
Essentially, you have to do it right first time or it might never be fixed.
Just to note, I disagree entirely. Even in commercial development, it’s the core premise of agile development to ship features early and continuously integrate feedback. Granted, lots of companies claim to do agile without actually doing it, but it’s at least not a law of nature what you’re describing.
But with this not being commercial development either way, I really don’t feel like you can make any predictions. If the volunteer that implemented this sees your bug report, they could decide to drop everything else and fix that, because they get to pick their own priorities. They might have the solution in their head right away and it doesn’t take them long at all to implement. Or someone new to the project might decide this sounds like a good issue to get started with.
The feature (boot manager) was not developed by KDE. They rely in systemd components which are all in active development.
So did you file a bug report or are you just being negative in a forum the developers will probably never read?
Right but presumably they chose the names?
It’s not a requirement to file a bug report before you comment on anything. Don’t be silly.
I don’t know.
It’s not a requirement but if anything is silly it’s acting as if an alpha version is the final release and complaining in a random forum would change anything.
What gave you the impression that I thought it would?
What gave the completely irrational impression that filing a bug report before commenting was a requirement?