Announcement
Collapse
No announcement yet.
Proposed Process Changes For X Server 1.8
Collapse
X
-
For years I've been waiting for a clipboard that remembers clips after I close an app. Finally, possibly there is hope.
-
Originally posted by nanonyme View PostYeah and if only all features took as long to be written and if only all coders wrote code as fast and... Oh, wait, it's impossible in practice?
Yes, we can read frustrated chief editors claiming "nothing exiting this month" etc. But, so what. They release. And they release smaller and gradual improvements more often, and, larger and more involving changes as well, but less often. Like it is expected to be.
So, I think this step is in the correct direction.
Leave a comment:
-
Originally posted by rohcQaH View PostHaving everyone release at the same time sounds good at first, but instantly upgrading every piece of software in a system rarely goes well, because nobody had a chance to test their release against everyone else's release beforehand. Imagine all those projects releasing today, and ubuntu just puts the new version on an iso and releases, too!
There has to be a sliding schedule, with the bottom of the stack releasing first, then the one next up. After an xorg release, the KDE/GNOME devs want some time to test their code against the new xorg before releasing. After the KDE/GNOME-Releases, the distros want some testing before shipping. etc
but all that is only important if you care about half-yearly time-based distro releases. I personally don't (gentoo), but many do.
This means that for (e.g.) Ubuntu 10.10 development to be started by May, apps should be in beta by May. And for apps development to be started by February, its components should be in beta by February. And so on.
Well, probably real life is more complex than that, but I think that if it makes sense conceptually, we should be able to manage ourselves to make it happen.
Leave a comment:
-
Originally posted by nanonyme View PostYeah and if only all features took as long to be written and if only all coders wrote code as fast and... Oh, wait, it's impossible in practice?
Leave a comment:
-
I love this proposal. I think it adapts terribly well to the nature of free software building; both for the effects on the project itself and for the effects on the rest of the projects that depend on it.
So, I think this idea should be not only implemented at X.org but also copied by other free software projects.
I think chaos can be tamed on the free software ecosystem thanks to this techniques. And if we achieve that, a resonance effect will emerge producing a wave of freedom that will smash window panes all across Microsoft offices. FUCK YES!
Leave a comment:
-
Originally posted by loonyphoenix View PostI'm shocked something like this wasn't proposed sooner. Those look like rather obvious things.
Peter does exactly that, and that's a good thing.
Originally posted by val-gaav View PostThis way Xorg, KDE , GNOME would have the same 6 month release cycle... If only those would be synced to happen at the same time ... Would be so nice...
There has to be a sliding schedule, with the bottom of the stack releasing first, then the one next up. After an xorg release, the KDE/GNOME devs want some time to test their code against the new xorg before releasing. After the KDE/GNOME-Releases, the distros want some testing before shipping. etc
but all that is only important if you care about half-yearly time-based distro releases. I personally don't (gentoo), but many do.
Leave a comment:
-
Yeah and if only all features took as long to be written and if only all coders wrote code as fast and... Oh, wait, it's impossible in practice?
Leave a comment:
-
This way Xorg, KDE , GNOME would have the same 6 month release cycle... If only those would be synced to happen at the same time ... Would be so nice...
Leave a comment:
-
I'm shocked something like this wasn't proposed sooner. Those look like rather obvious things.
Leave a comment:
-
Kudos to Mr. Hutterer for grabbing this massive, raging bull by the horns.
Leave a comment:
Leave a comment: