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."

Comments

if I was in charge of a FOSS project

[FudRucker]

I would release when it was ready, not when some stupid release cycle rolled around, that is what everyone does not need is some schedule to pressure developers to release before a product is ready...

Re:if I was in charge of a FOSS project

[maxume]

The idea of the schedule is not to encourage a premature release, but to encourage a sufficiently attainable definition of "ready" such that a release eventually happens.

Re:if I was in charge of a FOSS project

[InlawBiker]

There really isn't a perfect way to release Linux distributions. With timed releases components are prioritized quickly, but some stuff gets left out. With feature-based releases you have to wait until some number of components are ready so the release date is a mystery.

I think it's great the way it is: each distro has their own method, you can pick the one that's right for you. It's the ultimate in technical Darwinism.

Re:if I was in charge of a FOSS project

[RiotingPacifist]

OFC not specifying a schedule leads to e17, hurd, etc

Translation of Seigo's suggestion

[InlawBiker]

"Why don't you quite whining and help us develop and release the software you're re-packaging and trying to make money from."

This was a good article. The Internet was actually useful today.

Re:A lot of buzz

[garett_spencley]

"seriously, what sort of *nix system thinks you don't need a C compiler by default and makes you go looking for it in the repositories?"

One that targets non-developer desktop users ? Or even servers ?

As a sysadmin one of the many tasks I do to vanilla installs is to either uninstall the dev tools or restrict them to a particular group. Many exploits automatically download source for their rootkits or trojans etc. and compile it on the machine. Not having dev tools available to the user that the web server is running under, for example, makes these types of attacks more difficult and helps limit what an attacker can do if he does gain access (imagine a scenario where the attacker has no shell but can tell the web server to execute commands ... a simple 'wget' and 'make' later and he has himself a back door that gives him shell access as the web server user).

In other words, if you have no pressing need for dev tools then it's wiser not to have them installed. If you're a developer then you can easily add them via the repositories.

Sync would please ISVs

[HighOrbit]

I think syncing the major distro's would be a boon to Linux overall. It would make support easier for third party vendors and ISVs, which might induce them to release more major Linux applications. For instance, Oracle or Adobe whould know that a particular version of their product would only have to support a certain kernel (altough each distro has patches) and a certain version of Gnome and/or KDE as opposed to ten different point-releases of kernel,KDE, and Gnome. The would know which versions of the Gnu utililities they can expect to support.

Anything that makes it easier to for major software vendors to release and support software makes Linux stronger.

Way To Go Aaron

[mpapet]

Shuttleworth's idea is designed to further Ubuntu at the expense of the projects packaged therein. Specifically, he's trying to shift quite a bit of the release work onto the projects he packages.

Aaron's post is a must-read for anyone vaguely interested in the topic. In particular,
It is not overly dramatic to say that if we make Free software development overly sterile via choice of process, there will be a commensurate diminishment in participation and momentum. I interpret that as Aaron recognizing the corrosive effect on the entire dev community by adopting Shuttleworth's scheme.

Better still, Aaron offers constructive alternatives. It's really nice to read and should be a template for most blogging.

Someone please explain why Shuttleworth's idea hasn't been swatted down the day he posted it.

Today's lesson: Learn to disagree without personal attacks and offer viable alternatives.