Debian Leaders: We Need to Release More Often 460
daria42 writes "The lack of a new stable release of Debian GNU/Linux since July 2002 is fuelling the campaigns of many candidates for the project's Debian Project Leader role, with many pushing for a shorter and more stable release cycle to stop Linux users heading for greener and more updated pastures."
This is comical.. (Score:5, Funny)
I thought Debian was an enthusiasts distro..
Re:This is comical.. (Score:2, Informative)
Re:This is comical.. (Score:5, Insightful)
I believe the meaning of the word 'stable' is doesn't change often.
Or was it "So placed as to resist forces tending to cause motion."
stable as in stability, right? Isn't stability supposed to be a good thing?
That in mind, I do agree releases a year or so more often would help Debian. But for some people only having to update every few years is a great thing, they don't want upheavals on their servers every 6 months. This is the kind of people Debian stable serves. All of the rest use testing or unstable. They should make the website be more clear that stable is not for desktop users who want recent stuff.
There really isn't anyone working on Debian full time, and it's release pace reflects this. Debian is, well, different.
Re:This is comical.. (Score:2, Informative)
Unstable - changes often
for any slow people out there. English, anyone?
Re:This is comical.. (Score:5, Insightful)
The Debian project should really change their terminology if they don't want to scare people away unnecessarily. Any marketroid would tell them that it would be better to go with something like "Enterprise Edition", "Personal Edition" and "Exxtreme! Edition".
Re:This is comical.. (Score:4, Interesting)
If you were running for that Debian Project Leader Role, I would vote for you.
We're using SuSE because we can't use pacakges from something called "unstable"
Re:This is comical.. (Score:5, Funny)
Re:This is comical.. (Score:3, Insightful)
Any marketroid would tell them that it would be better to go with something like "Enterprise Edition", "Personal Edition" and "Exxtreme! Edition".
Anyone who cares about such things should go use RHEL. Debian is not about marketroid thinking. To those businesses who use more expensive, worse solutions than debian because debian's "modern branch" is called testing: their loss.
Re:This is comical.. (Score:5, Insightful)
Please! All the labels are arbitrary, as other commenters have pointed out. Stable, Unstable, and Testing? I've got a pretty good idea what 'Stable' is, but, without looking at debian's site, I can't tell you what the differences are between 'Unstable', and 'Testing'...
With that said, Waffle Iron's suggestions wouldn't work, either (however, I believe he was JOKING. Try turning up the sensitivity on your sarcasm detector. That might help you around here).
Perhaps something more sane like:
Except... (Score:5, Insightful)
Before there's a shitload of replies about 5 sucking - yes it did suck when it was strictly a new technology release. Now bugs have been patched and more things have come out from under the giant lock. Speed has increased, as has stability, and it has earned the -stable tag. The point of this post is just to say stable != extremely out of date. stability is just well-tested, well-written code.
packages (Score:3, Insightful)
FreeBSD doesn't have packages for most of things and for a few platforms. Compare that with releasing 12000 packages (14 CDs, IIRC?) for 10-12 architectures. Is not that FreeBSD sucks, they work great, but is not fair to compare two things that are not really the same. And BTW, the 4.X -> 5.3 step has not been exactly "fun".
(and don't come saying "this is the proof that ports > packages. Time has showed everybody th
Re:This is comical.. (Score:5, Insightful)
Re:This is comical.. (Score:3, Insightful)
There's one big problem with the Debian system: testing doesn't get security updates.
This is a myth. Testing gets lots of security updates, from both security.debian.org and through the extremely rapid propagation of "normal" upgrades that packages get. Most maintainers seem to propagate security-related bugfixes within hours.
If you use very rare packages with slumbering maintainers, you could probably be in loss of security upgrades, though.
well.. (Score:3, Interesting)
However, I do find that using a netinstall version of the "testing" release tends to keep up to date with most packages.
Re:well.. (Score:3, Insightful)
I've heard it mentioned that some packages are keeping things back, and by the time those packages are ready, there are others being kept back. it's a duke nuke'em kind of situation
Why not aim for a 12-monthly release? Go over by a month or two if absolutely needed, but aim for that. Even if some packages were missed the first time around and left the same as
Re:well.. (Score:5, Insightful)
Re:well.. (Score:2, Informative)
You're probably refering to d-i which does have snapshots which get updated every now and then, but it itself is updated all the time.
Maybe a bit too often... (Score:3, Informative)
I would prefer something in between stable and testing, updated reasonably often with new packages (and features) and also have security releases in between as required.
Re:Maybe a bit too often... (Score:3, Insightful)
If you'd been reading the rest of the discussion you would have noticed that people suggest that the stable distribution is more appropriate for server type environments where stability is paramount. I'm merely suggesting a 'stable' distribution more appropriate for general use (such as mine).
Your post contributes nothing to the 'solution', so I suggest you become a part of the solution instead of being a jackass.
Re:well.. (Score:5, Interesting)
My guess is FOSS really took off unexpectingly and Linux became ported to more architectures besides x86 and the Alpha. This caused the folks at Debian to focus on everybody including the atari users.
If a bug was fixed for most platforms but the amiga users (all 15) was still present, then package X would not be updated on any of the other releases. This is whats hurting it.
I hate to say it but the x86, powerpc, and sparc versions should be ahead and have a later version then the others. FreeBSD for example has alpha and powerpc as different tiers of support, although alpha is still pretty stable.
Re:well.. (Score:3, Informative)
If it's stable, it doesn't need to be updatedOften (Score:5, Insightful)
Re:If it's stable, it doesn't need to be updatedOf (Score:5, Informative)
Speaking of which... *tap* *tap* is this thing turned on? Is anyone from the Debian security team listening? I've got a security issue here... I've e-mailed vendor-sec (3 weeks ago)... I've e-mailed debian-security-private directly (1.5 weeks ago)... are you guys planning on responding some time this month?
(Yes, I'm entirely serious. Slashdot isn't my preferred channel for communicating with other security teams, but the usual mechanisms seems to have failed, and I figure that there must be at least a few Debian people reading this story.)
Re:If it's stable, it doesn't need to be updatedOf (Score:3, Insightful)
They can contact the teams in other methods I'm sure, and if not, they can publish it and force a fix.
Re:If it's stable, it doesn't need to be updatedOf (Score:5, Informative)
Re:If it's stable, it doesn't need to be updatedOf (Score:3, Informative)
A notable problem with using "spinoff" distributions is package compatibility. Can I install any
This is a problem with rpm-based distributions; I don't know if apt handles it in a smarter way than rpm, but I've been burned by it and I'm hesitant to tr
Re:If it's stable, it doesn't need to be updatedOf (Score:5, Informative)
-Leigh
Re:If it's stable, it doesn't need to be updatedOf (Score:4, Insightful)
AFAIK, packages within Debian itself aren't even compatible with each other. If you're running unstable and you want to give a package to someone running testing, you're out of luck. Why is it a surprise that Ubuntu packages wouldn't be completely compatible? From my experience with Ubuntu, it seems like most Debian unstable packages are forward compatible to Ubuntu, but I doubt the reverse is true. This makes sense. Ubuntu has more up to date packages than even unstable at some points, since Ubuntu applies it's own patches, and the Debian maintainers may not apply them immediately. If they add the Ubuntu repository at a low priority and try installing your package, it'll probably work, but some of their libraries will be updated to Ubuntu versions. That's a bad thing, because it might break future updates within unstable for them. Maintaining package compatibility and achieving Ubuntu's goals at the same time would be impossible to do.
By the way, Ubuntu isn't a "spinoff" distribution. It stays with Debian unstable, then freezes the set of packages and stabilizes them. For the next release, they start over.
Re:If it's stable, it doesn't need to be updatedOf (Score:3, Informative)
Actually...Yes. Yes you can
In fact the system I'm writing this on is Ubuntu Warty and I have the Debian Sarge repositories loaded in my sources list. I've got quite a few Debian packages loaded on my system with no breakage whatsoever. I've heard people refer to this type of setup as "Debuntian
Comment removed (Score:5, Interesting)
Re:More stable releases please (Score:5, Insightful)
If the release cycle were to be shortened to said 18 months, it would be nice if Debian were to maintain older releases and not only the previous release, like it it now.
I recommend Debian to my customers as a server platform, exactly because it has the finest package management and the longest release cycles. When stability is the goal, Debian is the right choice!
Re:More stable releases please (Score:3, Interesting)
Three levels just isn't enough to grade sensibly from known-near-perfect to bleeding-edge.
J.
Re:More stable releases please (Score:5, Insightful)
I mean the windows world and the linux world are two totally different beast's and i will admit other distro's really have taken two steps forward in the stable branches compared to debian woody but the basis is still the same and IMO debian really does the same job better then a few other current distributions.
In the server world I really only rely on Debian for the mission critical stuff and you know what? So far so good....
Re:More stable releases please (Score:3, Insightful)
Whereas Windows is just an O/S, a Linux distribution is an O/S and a pile of applications. This is often considered to be an advantage, but it can be liability, when it comes to long release cycles. For a lot of situations, I'd be comfortable deploying Linux 2.2, glibc 2.1, and even Apache 1.3. I wouldn't necessarily be as comfortable with the Python 1.5, PHP 3, etc., to say nothing of the desktop components. I could build newer versions of the r
anecdote (Score:5, Funny)
Debian was the first Linux distribution I ever downloaded, in the summer of 2003. I was on dial-up at the time (and didn't even have my own line, so I couldn't download 24/7), and I remember being worried that there'd be a new release by the time I was done downloading the first ISO. I mean, open-source software moves fast, right?
Should've relaxed.
well, are you done downloading yet? (Score:5, Funny)
debian (Score:2, Interesting)
Duh... (Score:5, Interesting)
Bruce
Re:Duh... (Score:2)
Re:Duh... (Score:5, Informative)
Bruce
Re:Duh... (Score:3, Interesting)
If you really want UL to be 'something' and 'out there', why not just do the required work, and 'get it out'. If you have to wait for a debian update, where is the value add in the UL?
Re:Duh... (Score:5, Informative)
Historicaly, I am the author of Debian's fundamental policy document and did a lot of the early work on their system.
I've paid my dues a few times over.
Bruce
Re:Duh... (Score:3, Interesting)
Re:Duh... (Score:5, Interesting)
The policy of the UserLinux project is for all development to be carried out within Debian, not within our own repository. Customers can take a much greater role because the Debian organization admits them fairly.
Of course, the long release delay has made something of a fool of me - because so far we've only proven that this non-profit can't get it together to make a release.
There is a lot more in the white paper on the project site.
Bruce
Re:Duh... (Score:3, Funny)
OK. What's your name and address?
Re:Duh... (Score:2, Funny)
Re:Duh... (Score:5, Informative)
Check it out - I'm certain that they'd like the help of a high profile advocate like Bruce Perens.
Soko
Re:Duh... (Score:2)
Re:Duh... (Score:3, Interesting)
Re:Duh... (Score:5, Informative)
When comparing Ubuntu with other distributions than Debian, things are a bit different. One of the selling points for Ubuntu for me is that it's developed by a community and has a central package repository. It's been a while since I used a non-Debian distro, so I'm sure much of this has changed, but when I used Red Hat and Mandrake, there was either nothing that compared, or it wasn't visible enough. Assuming that other distros have that now, there's the deb vs. rpm issue depending on which one you prefer. The main issue is that you're never considered a second class citizen in Ubuntu. The other distros have commercial versions with special software and updates you don't have access to. With Ubuntu, everything is free, and they've made a commitment to always remain free.
Re:Duh... (Score:5, Informative)
Has recent packages (Woody doesn't)
Provides security upgrades (Sarge doesn't)
Is somewhat stable (I believe that Warty is stabler than Sid)
Many packages in Sarge are newer than their counterpart in Warty, and similar Sid has newer packages than Hoary. However these differences are small and unimportant.
Ubuntu has focused on a subset of the Debian archive. The packages in this subset are stable and work well. Furthermore Ubuntu has a "universe" archive that contains most of the packages in Sid. Some of the universe packages are uninstallable due to missing files. This can be bad if you are very dependent on a specific program.
Re:Duh... (Score:4, Insightful)
Actually the first time I tried Debian, unstable was broken rather often. Only for a few hours in most cases but broken nevertheless. I switched back to Debian when Knoppix came out (point in case: forget Ubuntu; use Knoppix to get a Debian unstable configured and installed in less than an hour =) and I haven't seen a unusably broken package since (In two years? Not sure how long it's been. Did a system reinstall after a hard disk crash). Recently the autofs package's post-install didn't work but the program itself worked just fine.
Re:Duh... (Score:3, Interesting)
I switched to Mandrake, but really couldn't stand urpmi: it's soooo slooow! Honestly, why does it have to download a multi
Debian thoughts (Score:5, Interesting)
Re:Debian thoughts (Score:5, Insightful)
So using Debian derived distributions like Ubuntu or Knoppix is still good for Debian, or at least compatible with its goals.
The fact that it's a pretty good distribution in its own right is more or less just a bonus....
Have to compete with Microsoft (Score:5, Insightful)
Re:Have to compete with Microsoft (Score:5, Insightful)
A version of Windows from 2001 isn't a problem, but it would be if it couldn't run more recent programs.
Re:Have to compete with Microsoft (Score:3, Insightful)
Secondly, Windows XP is just the a basic operating system. Debian 3.0 has 8710 packages bundled with it, and all of those packages are now almost 2 years old.
Running a 2002 release of Windows XP doesn't prevent you from installing the lastest version of Mozilla, Firefox or . The version of Mozilla in Debian stable is currently 1.0.0, and Firefox isn't even there!
I've been running debian servers for the last 5 years, but lately I have been s
Yeah... (Score:4, Interesting)
I guess that it'd been awhile since I last installed Debian from scratch, I didn't know that it has been two years.
this just in... (Score:2, Insightful)
Debian Leaders: We Need to Release More Often
This just in: the Catholic Church says the Earth is round.
In other news, George Broussard admits Duke Nukem Forever "is a little late".
Question- why did it take, oh, 3 years for them to finally come to terms with the fact that their iguana was turning into a dinosaur? It's like they've all been collectively in denial. I took one look at the list of versions in the stable branch when someone suggested I check out Debian. I laughed, and closed the window
Re:this just in... (Score:5, Insightful)
Re:this just in... (Score:3, Insightful)
Okay. So, again, why did it take three releases to realize something was wrong? If the symptoms were known, why didn't people just start fixing them? Politics? Funny thing about politics. Even if the politics aren't in your favor, if your intentions are honest, you're stepping up to the plate when no one else i
Re:this just in... (Score:5, Informative)
After potato was released, Anthony Towns implemented testing in an attempt to keep testing in a releaseable state always, so releases could occur more rapidly. That helped, but still didn't really fix the problem.
After woody was released, security support and the installer were serious problems that had stalled the release of woody for quite some time, so more effort was placed into those areas to create a working installer along with a decent security infrastructure. That has helped as well. However, it took quite a while for those to be implemented.
Now that sarge is on the verge of being released, people are analyzing the situation again to try to figure out what else should be done to fix the problem. The Vancouver Prospectus [debian.org] is an attempt to solve what have been identified as the problems for etch.
No, as you can see above, specific things have been attempted to solve the problem. They haven't succeeded, clearly, but it's not for lack of trying them. Distributions based on Debian are rather easy to make, frankly, especially if you're going to standardize on a specific set of packages and only support them. It helps as well if you can throw money at the problem and hire people to work on specific problems. Point in fact, none of the not-for-profit Debian based distributions have every actually released a stable distribution and suported the entire stable distribution for a whole product life cycle. They have different goals for the releases that they make than Debian does, which is quite acceptable for them. [Nothing is stoping anyone from taking a specific version of testing, calling it "stable" and supporting it. The fact that no one has should tell you something.]
Re:this just in... (Score:4, Informative)
The actual blocker for the past 6 months or so has been the testing-security support. Before that, it was the fact that we didn't have a working installer.
Not a huge deal (Score:4, Insightful)
I don't really care that it's not updated because apt is flexible enough to work around that. And if a package is _insanely outdated, usually a newer one is in Testing or Unstable. And as a last resource, it's not like Debian precludes you from compiling it myself.
While more frequent releases would be nice, I like it just the way it is. I feel as if I'm guaranteed that the packages will work together without problems (something I haven't encountered in certain other package management systems). And for the select few programs where the version is unacceptably old (like gaim), I just compile from source code.
Too much pr0n... (Score:2, Funny)
And I, for one....
ahhh, never mind.
Good news, I think (Score:5, Interesting)
I've been a Debian fan for some time, but I find I am racking my newly built critical servers on RHEL3&4 just because so many of the Debian packages are 'stale'. In a lot of enviroments, running testing is unacceptable and using stable is to far out of date for the intended use of the machine. We are definatly in limbo as far as Debian installs.
I really hope they pull this together, without Debian the landscape changes dramatically for binary stable systems.
But, the biggest problem I can see is that by releasing early and often it creates a larger legacy code base that needs to be maintained but does not have the resources to do so. You cannot effectly update a server farm of hundreds to thousands of machines to a new version within a short legacy cycle, yet it is a huge burden to maintain the legacy code for any lengh of time.
Even Slackware.... (Score:4, Interesting)
There's no excuse for no Debian stable releases since 2002.
Maybe Bruce should base UserLinux on that.
--
BMO
Re:Even Slackware.... (Score:4, Informative)
Re:Even Slackware.... (Score:3, Informative)
There's nothing wrong with the Slackware package management. It doesn't have dependencies; that is by design. Otherwise it's not too different from anything else, except Gentoo.
Debian appears.... (Score:4, Insightful)
Anyway, if you look at it that way, it's neither way behind the times or bleeding edge, it's just a big ole pile of apps and kernels that you have access to. Maybe they should just skip the different versions, let Apt sort it out when people go to build their own, make it a remasters dream system instead of trying to be a stock classic distro "OS". Do something different than what MS and Apple and Sun are doing. Make the personalised "your computer" be the primary focus, along with the "easy" part.
Not sure about more stable releases (Score:2, Insightful)
There is one very easy way the Debian team could achieve this: merge security patches into Testing at the same time as Stable and Unstable.
Why would this be a good idea? I can't be bothered re-iterating, so here's a paste from a prior post:
Stable? Sadly, not an option due to its complete lack of support for modern hardware or moderm features
I most certainly agree! (Score:2)
Most of the things I needed were in unstable (at the time it was potato I think), and unstable was breaking various odds and ends on a weekly basis and I didn't trust it at all so
Why? (Score:2)
no shit, einstien! (Score:4, Interesting)
Re:no shit, einstien! (Score:5, Insightful)
Lee
Re:no shit, einstien! (Score:5, Insightful)
I've given up on yum and up2date and switched to apt and synaptic on FC3. Works like a dream. Mirrors can be set up within a CLI for apt. The synaptic GUI is excellent. Fedora semi-officially maintains the apt database but the apt database is always the last to be updated when rpms are updated.
yum and up2date existence is very questionable. They're fundamentally designed around the idea that no new packages will ever get added to the distribution after release. But the Fedora team has a religious attachment to yum so things will continue to suck for new users.
Re:no shit, einstien! (Score:2, Insightful)
Re:no shit, einstien! (Score:2, Flamebait)
Re:no shit, einstien! (Score:2)
Re:no shit, einstien! (Score:3, Informative)
Re:no shit, einstien! (Score:2, Insightful)
Re:no shit, einstien! (Score:3, Informative)
If you're willing to switch to a different OS altogether, try FreeBSD. FreeBSD has a Package and Ports system. Packages are pre-compiled binaries that can be fetched and installed, and Ports is a way of installing software through source.
To install Firefox, for example, you can type pkg_add -r firefox, and it would fetch a Firefox binary from the FreeBSD servers and install it from your system. If you prefer to compile Firefox, just cd to /usr/ports/www/firefox and type make install clean. It would aut
Hey. (Score:2)
I never thought of Debian as having releases (Score:5, Insightful)
Stable
Testing
Unstable
Each have their own rewards and risks, but the key to me, was that with the netinstall disks, they never went out of date. You never had a CD set full of six month old packages, you had your favorite debian versions latest, usually day old release, a download away.
The new installer is excellent, and with the lack of X based GUI, will still work with a minimal download.
Re:I never thought of Debian as having releases (Score:5, Interesting)
Trim down the number of "official" packages. Right now there is something like 3000 packages in the debian system. Why not cur that down to a thousand. Take the top 1000 most popular and best maintained backages and call it debian.
The rest of the packages can go into "ports" or "contrib" or something. They would still be there if anybody wanted to install them but they would not hold up release cycles, debian would not guarantee they would work with the rest of the system.
The great thing about debian is that by using stable you are promised that nothing you install will break your system. They can still promise that but just with less packages.
15781 packages in sid-main-binary-i386 (Score:3, Informative)
This is why I changed to Gentoo (Score:2, Insightful)
I changed to Gentoo because a lot of the new software took far too long to be released as a debian package. Sure, I could have just downloaded the software, make install, etc blah. But I wanted to manage my packages!
For this very reason I switched to Gentoo.
The only thing annoying about Gentoo is compiling time - which is still quicker than waiting for Debian packages to come out.
What's the problem? (Score:5, Insightful)
On the other hand, the fact that derivatives are necessary is a sign of Debian's shortcomings. I haven't used Mepis in over a year, but the last time I used it, it was basically Debian installable off of a live CD with easy to use configuration tools. That says that Debian proper is hard to install and lacks user friendly configuration tools. The former problem has been fixed, but I'm not sure the latter has been. Ubuntu is Debian with a shorter release cycle and paid developers to add polish. This shows that users obviously take issue with Debian's long release cycles, and once again, the administration tools. Anyone who is running the development version of Ubuntu right now knows how easy it is to keep things up to date. The newer software also takes advantage of advances on the Linux desktop, such as Project Utopia. I can plug in USB devices, and they just work. It's nice, and Debian proper misses out on things like that because of the age of its packages.
So who uses Debian stable? From the things I hear, it's people who want a long release cycle. Woody users have been getting security updates for however long it's been since the release. People like that. Ubuntu is supported for 18 months after a release, which is likely to be too short for some people. I don't see how Debian loses out from desktop (and some server) users using the derivatives. Ubuntu is the main derivative, and all its work goes back into Debian proper. When etch is getting ready for release, the job is going to be much easier to do, since Ubuntu has already done much of the work ahead. Sarge has been in some sort of a freeze for most of the time Ubuntu has been around, so they haven't been able to reap the benefits of Ubuntu's presence. People getting paid to work on Debian is a good thing, not something to be angry about, which is the sense I get from some posts on Planet Debian.
So if Debian shortens its release cycle, where does that put it in the Linux ecosystem? I doubt they will be able to support security updates for multiple stable releases, which is what they would have to do with a short release cycle to maintain the current length of support. As much as Slashdotters like to poke fun at Debian, it plays a very important role. Does it really need to change?
Debian developers, thanks for making such a great distribution. There are lots of Ubuntu, Mepis, and Debian proper users that appreciate it.
#1 Reason Why I Don't Choose Debian For My Bus. (Score:3, Interesting)
[hypothetical scenario]
Customer: "What operating system version do you use?"
Us: "Debian unstable."
Customer: "...unstable??"
The close-behind #2 reason is the installer, but I understand that's getting fixed. IMHO, Debian should strive to release a new stable version every 6 months, with 12 months being the maximum time between new stable releases. As it is, I cannot justify using Debian for business purposes when their offering that coincides with what we need is labeled "unstable".
Question? (Score:2, Funny)
whats the only thing that takes longer than a full Gentoo compile....
food for thought (Score:5, Funny)
redhat: the cafe food in the basement of the megacorp, great food but at airport restaurant prices.
novell/suse: the suits come in the front and pay to sit down and get served the same great food most of which is given away at the soup line in the back.
white hat: sneaks the food away from redhat and does the soup line thing. Some seasoning missing.
mandrake: tastes like redhat with somewhat better seasoning and operated kind of like the suse restaurant
gentoo: gourmet ingredients for you to build your own 9 course dinner, hopefully you don't starve in the meantime
debian: stale, week-past-expiration date bread that won't hurt you, and some rather tasteless but nurishing year-old jerky to put on it.
debian (Score:4, Interesting)
the fuss about Debian's "cycles" (Score:5, Interesting)
For one, people should really understand and see, that not all Linux distributions are just there to suit the newbie (l)users' desktop needs. This is just the attitude people gather while being full-blown Windows users and then fiddling around with some Linux, thinking it's cool and if he can't find his way around, then at least that';s another reason to bash.
Debian's stable branch is just _the_ perfect distro for servers. You can argue with this statement, but I will _not_ listen to home users' hysterical crap about the newest kde/gnome being necessary. There are places where that simply doesn't matter.
Where I spend my working hours very few people use Linux distros on their desktops, really very few, but almost all our servers are Linux based. The two of them where I hve root access are Debians. One is a current stable Woody, being web&mail&db&cvs&related server which I installed last year because the previous machine had a major blowup. The other is a Debian Potato (!) which is the previous [i.e. before Woody] stable branch, which is our dns server, up and working for
No desktop environments, no x, just good stable and reliable code which I trust and - most importantly - _very_ _easy_ to maintain.
At home I use Debian SID for about 4 years now. Updated about weekly, _very_ stable and usable. It has all the desktop fun I need. Most important: it hasn't been reinstalled since the first install just always copied over to the changed machine (about once in a year, I always hand-build my machines ever since I became acquainted with the screw driver), updated the necessary stuff and keep it always apt-get dist-pgrade-ed.
For me, and for many others out there, Debian - and now the quite many Debian-based distros, hey, there are even Debian SID-based distros now (!) - represent _the_ _GNU/Linux_ _distro_. For the others, there are plenty of others you can use and that is exactly why Lnux distro forking is a Good Thing, try not to forget that.
Re:the fuss about Debian's "cycles" (Score:3, Insightful)
1- woody + backports or handmade packages is NOT woody. why ? because you have to _maintain_ it by hand (or trust the backporters to do so efficiently).
in other words, woddy+backports or handmade packages is NOT anymore a stable distro. and, i agree, stability is something important for a server, and especially in a company.
2- it's becoming almost impossible to be able to use an unmodified woody on a server, because of the various reasons i've written down. and i'd say it's th
Project Management 101 (Score:5, Interesting)
Personally I think they would be best served by doing a little of each.
Re:Project Management 101 (Score:4, Insightful)
I disagree. One of the greatest things about Debian is the scope of the project. I can install almost anything and not have to hunt around the internet for a package. It's all in one place. I think the currently proposed approach on not releasing the lesser used architectures at the same time at the others is the correct approach. Abandoning them completely would be foolish, but having a whole release held back by problems with software that's not even heavily used is a problem.
Add development resources
This has been done. Ubuntu. People are paid to work full time, and their work goes straight into Debian. This also takes care of the issue Slashdotters have with the long release cycles, since people can download a new version of Ubuntu with the latest version of Gnome, KDE, etc. every six months. The problem it doesn't solve is that of people who want to run Debian stable, but can't use the ridiculously old packages for commonly used web programming languages. The release cycle needs to be shortened, but not by too much.
reduce some of their bureaucracy and excessive policies
You call the policies excessive, but it's thanks to their efforts that is possible to run a computer based on completely Free software (and Free documentation, which is probably the issue that prompted this point). Sure, their policies often err on the side of idealism rather than pragmatism, but I think it's beneficial for the entire community that they do this.
Misleading Nomenclature (Score:5, Insightful)
It's an absolutely massive project. There are about ten thousand packages, all including metadata for full automatic dependency checking and resolution. Each of these packages is available for each of a dozen architectures, and there is consistency across all platforms. Debian is Debian; whether it's running on an Intel, a PPC, a Sparc, an ARM or whatever. The user need not know what lies beneath the skin of the machine; the procedure for doing something should be absolutely the same whatever is inside.
For a project of that sheer size to work, it's pretty much got to be ruled over with an iron fist -- if not literally, then those involved have to act as though it were so.
Woody is out-of-date for desktops; I don't think there is any question of that. KDE 2.2? Hello? And it's not exactly up to the minute for servers, either: it's still pushing Apache 1.3, for crying out loud!
The real problem stems from the fact that before a package can be accepted into the Stable release, it has to be shown to be bug-free on each of twelve architectures. So if it segfaults on a steam-powered toaster, it can't be deemed fit to run on an 80386.
But that's just the ideal for the Stable distribution. There are two other Debian distributions, Testing and Unstable. Whenever someone creates a brand-new
Testing is actually the Debian distribution you probably really want to be running if you have an 80386-type machine. Yes, security updates get ported into Stable in good time; but Testing probably has newer versions of packages anyway which are likely to have the security patch in by default. It's safe to run on servers iff you read the news and you know how to apply a patch and compile a package from source. {And if you don't, then what the hell are you doing running a server?} But Unstable is actually quite reasonable. I've found it to be no worse than Fedora or Mandrake: any problems I've had with packages not installing or not co-operating turned out to be due to mis-specified dependencies, requiring cunning use of manual override and package searches. So no worse than any RPM distro there
It's also worth remembering that every Debian-derivative -- Ubuntu, Linspire and so forth -- started out as a copy of the Unstable tree.
Re:Speaking of which, Suse 9.3 next month (Score:3, Insightful)
Not to mention... (Score:3, Interesting)
But I'll wisely keep quiet so not to incur the wrath of Slashdot...