Slashdot Mirror
Shuttleworth Calls For Coordinated Release Cycles
voodoosws points out on Mark Shuttleworth's blog Shuttleworth's call for synchronized publication of Linux distributions, excerpting: "There's one thing that could convince me to change the date of the next Ubuntu LTS: the opportunity to collaborate with the other, large distributions on a coordinated major / minor release cycle. If two out of three of Red Hat (RHEL), Novell (SLES) and Debian are willing to agree in advance on a date to the nearest month, and thereby on a combination of kernel, compiler toolchain, GNOME/KDE, X and OpenOffice versions, and agree to a six-month and 2-3 year long term cycle, then I would happily realign Ubuntu's short and long-term cycles around that. I think the benefits of this sort of alignment to users, upstreams and the distributions themselves would be enormous. I'll write more about this idea in due course, for now let's just call it my dream of true free software syncronicity."
Seriously, this would be a boon for Linux development in general, filling in the big gaps left by the LSB.
- None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
Simultaneous release schedules = simultaneous betas = testers spread more thinly.
First thing I thought of is being able to mix repos of several distributions. I don't think RH and Novell will do it, just for that reason.
Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
While that sounds a bit snarky, there's a serious point.
Users often want to have access to the latest software. Many distributions provide updated packages over time, so that when a new official release comes out, many users already have a good portion of the changes. Gentoo takes this to the extreme, having eliminated the concept of release entirely (except for the installation system). So how does a synchronized release schedule help anyone when users will be upgrading various packages when they are updated?
I just don't see the value in synchronizing releases.
I think that's half the idea -- to provide an external motivator for packages to wrap things up and release something stable periodically.
The other half of the idea is that it provides a more uniform platform for software/hardware support -- the idea being that Adobe or NVidia could make a release that works with all the March 2019 distros, and support people could offer support for the March 2019 distros. It is, after all, one thing to be familiar with the package management of 5 different distros, and another thing entirely to be familiar with the specific point release quirks of the software packages on 5 different distros.
Of course reality would be nowhere near as elegant as this theory.
Recursive: Adj. See Recursive.
I'm surprised that nobody yet has mentioned the most obvious reason why Shuttleworth would want this.
Canonical shipped shipped their latest Ubuntu release, 8.04 ("Hardy Heron"), last month. Canonical wanted Hardy to include Firefox 3 instead of the getting-a-bit-long-in-the-tooth Firefox 2. However, since Mozilla's release target for FF3 was a month after the release target for Hardy, Ubuntu had three choices, none of them ideal: put off the move to FF3 for the next release (six months down the road), ship Hardy with a beta version of FF3, or delay shipping Hardy until FF3 had shipped. They ended up shipping with Firefox 3 Beta 5.
This matters because Hardy is a so-called "Long Term Support" (LTS) release, which Ubuntu commits to supporting for eighteen months instead of the standard six (for customers who don't want to be updating their OS every six months). So now Canonical is on the hook to support a beta release of Firefox until long after FF3 final is released and the betas are forgotten.
I would presume that Shuttleworth wants coordination in distro release cycles because it would give him more leverage with third parties in situations like this. If Canonical says to Mozilla "hurry up and finish FF3 so we can make our release date", that's easy to ignore because it's just one distro. If EVERY distro is saying that to Mozilla, they'd be more inclined to listen -- and probably more likely to orient their own release cycles to fit with those of the distros.
Read my blog.
There's absolutely nothing reasonable about Shuttleworth's request.
1. It's a Trojan Horse to legitimize Shuttleworth's business prospects. Simultaneously he'll out-shout Debian and give him a platform with which to more easily compete with Novell. Given Novell's history of mismanagement, I'd say they are helping him already.
2. There will be _lots_ of ubuntu users ready to mod me down for comment #1. Let's entertain the notion that I am completely misguided and I fall in line with the Ubuntu groupthink. What exactly would be accomplished? Nothing. Ubuntu already forks from Debian early on and as far as I can tell, never the twain shall meet.
3. Debian still releases when ready. Ubuntu releases on a calendar, warts and all. Imagine if the Debian community fell under Shuttleworth's and changes to a firm "ready or not" release schedule. It would slowly turn the Debian project into Shuttleworth's fiefdom rotting it from the inside.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
No, I don't, nor does anyone else worth considering as a requirement from the overall Linux community. But that's not what I said.
What I said was the frequency of opportunity to switch is important. Right now, if your distro doesn't do what you need, but another one issues a release that does do it, you can switch. Any one person might switch that way only once in 10 years. But overall, thousands of people probably switch that way every time a new distro is released with significant differences in version or inclusions from the last significant release of any distro.
Many more people probably do so at the even finer granularity of unofficial updates to existing installs, but that's not the same as getting an official release, with all its support, and even with support contracts (like with the distros Shuttleworth is talking about). Which is why we're talking about the actual release schedules, because unofficial updates are so frequent and self-organizing that they don't need to be synchronized. It's the value of the full, supported (and tested) releases that Shuttleworth and I are talking about.
--
make install -not war
Yes, but I have found that new versions of software often have bugs in them. Sometimes causing system failure.
If Suse or RH want to hold back on a new release or RH wants to jump up and be the beta tester for a new version then more power to them. I think that while Shuttleworth may be well intentioned, it would ultimately be a disservice to the linux community for multiple reasons. Security and reliability being the number one reason.
I really think Shuttleworth knows this and is making this statement more to get advertising for his distro than for anything else.
RH and Novell have large customers and are well acquainted with their needs. If in the process they find that certain packages cause problems, they may postpone a release. RH and Novell accepting a release cycle plan based on the communities "We just want to know" or "I have a dream", just isn't going to be a good business decision at this time. And I don't think it makes sense for the Linux Community as a whole either.
I actually stumbled across this last night on firehose or something. No comments had been posted yet and I thought it was a joke along the lines of something in the Onion.
He who said 1,000,000 monkeys on 1,000,000 typewriters would eventually type the great novel, never saw an AOL chat room
The Bazaar will survive. There'll still be Puppy, PCLinuxOS, Mandriva, MEPIS. Gentoo, Slack/Slax, CentOS, Arch, Vector. NetBSD, FreeBSD, OpenBSD, DesktopBSD, PC-BSD. OpenSolaris. gOS, Xandros, Freespire.
The Bazaar and the Cathedral is not a dichotomy. It's symbiotic. They not only can coexist, they must.
The Bazaar certainly will survive this because of the people behind it. If Shuttleworth's clan strays to far towards the Cathedral, the Bazaar's backers will throw their weight elsewhere.
But if Canonical never does anything to provide services to the Cathedral, only the Bazaar - no matter how vocal, always the minority - will ever benefit.
The people who only have time for the Cathedral's simplicity benefit from collaboration, and the people with time to sample everything in the Bazaar benefit from competition. It's long past time for the Bazaar and the Cathedral to work together and share those benefits with each other.