Slashdot Mirror


It's Not Time for OSS Release Cycle Synchronization

Bakkies Botha writes "Ars Technica weighs in with some detailed analysis on the controversial issue of open source release cycle synchronization. Ars explains how time-based release cycles work and takes a close look at how the release management strategy suggested by Ubuntu founder Mark Shuttleworth would impact open source software projects. Ars concludes that Shuttleworth's proposal isn't currently viable and argues that the BFDL is overstating the potential to simplify development with better version control tools. Ars also examines a counter-proposal offered by KDE developer Aaron Seigo and explains how it enables users to get the same benefits of synchronization without disrupting upstream development."

3 of 110 comments (clear)

  1. mqod down by Anonymous Coward · · Score: -1, Troll
  2. Counter Proposal by Anonymous Coward · · Score: -1, Troll

    Go fuck yourself, Mark

  3. Re:Oh wow! by Anonymous Coward · · Score: -1, Troll

    You don't think his recent, direct involvement with the release management of one of the largest open-source projects in existence has any relevance to the value of his opinion regarding open-source release management?

    What, we're allowed to point out when people in the proprietary world have fucked things up, but as soon as somebody's code is open-source, suddenly everything they do is puppies and rainbows?

    No. His attitude towards release management totally screwed up KDE 4. I personally switched to GNOME due to the corresponding plummet in quality, and I've been using KDE since the 90s. I think it's fair to mention that when he thinks he has a good plan for release management, especially when he totally denies causing problems and blames users for expecting too much from KDE 4.0.