Linked by Thom Holwerda on Mon 19th May 2008 18:40 UTC
Back in April 2008, Canonical's Mark Shuttleworth pitched the idea of major open source projects synchronising their release cycles on a 6 month period. Projects like gcc, the Linux kernel, GNOME, KDE, as well as the distributions, would work out an acceptable release schedule. It would allow for easier collaboration between the various projects, and hardware vendors would be better able to support Linux since all major distributions would ship with the same kernel version.
Thread beginning with comment 314943
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
Same difference. Whether it's Ubuntu's or Gnome's timetable it doesn't solve the problems.
All projects have their own goals for each release, and as Aaron pointed out, for projects who have a timetable of major structural changes and want to get more far-reaching features implemented, which happens from time to time, a six month release cycle is an total ass.
Aaron is spot on to be sceptical about strict time based releases. Quite often, and Gnome has suffered terribly from this, major features and changes that should be made are continuously put on the backburner for future releases because the next release just comes up far too fast. Just because you can make a release, it doesn't mean that there's anything actually in it. From that we get the suggestion of better branching so that features can be backported more easily. It's all in the articles.
KDE does have time-based releases actually, but they're not willing to be strict about them because open source development just isn't like that.