Slashdot Mirror
Debian Delayed by Disenchanted Developers
Torus Kas writes "Debian GNU/Linux 4.0 was supposed to be due by December 4 and development is currently frozen. Apparently the saga was triggered by disenchantment towards funding of $6,000 for each of the 2 release managers to work full-time in order to speed up the development. Many unpaid developers simply put off Debian work to work on something else."
>> "Cut the distro down to what will fit on one CD (two max)...."
:-)
dont do it Debian... its great to be able to apt-cache search and apt-get install almost anything. such a huge collection of available software that JUST WORKS is great. a little (or lot) longer release cycle doesnt really effect the bulk of users who just use "testing" anyway.
my 2 cents. Debian's base of huge packages, and apt are great assets. apt-get into it
I don't agree with you on this one. The biggest power of Debian is that most packages, even obscure one, fit into one distribution with all the testing and dependancies being resolved. I have experience with Red hat, Suze, and solaris (ouch on that one) systems where installing off the beat application can sometimes be hell. Debian provides a quick way of testing application before deciding to start a buld process where you get to spend half your evening building the newest of the newest libraries. Been using Debian since Hamm and I hav gotten used to delays... If you feel lucky you can always dist-up to Unstable.
open source is often made by paid developers, including major chunks of the Linux kernel. Open source just means you get the source code to modify or inspect, nothing to do with compensation or lack thereof.
hiring some full-time workers seems to have had precisely the opposite effective of the intended.
not workers... managers. I think most technical/coder/slashdot types have the same general opinion of managers and management (*cough* parasites *cough*). Many open source projects have paid individual programmers with no backlash. And many companies pay for programmers to write open source code. Sometimes it doesn't work out (ie, the XEmacs/Emacs split), but it doesn't usually outrage other developers.
Do you even lift?
These aren't the 'roids you're looking for.
This email from October 26 is pretty darn informative when it comes to dunc-tank. http://lists.debian.org/debian-project/2006/10/msg 00260.html
6 /11/msg00004.html
/.ers just go straight to http://www.debian.org/News/weekly/ and get the news. I certainly wish the editors at /. would.
This email from November 16 will pretty much bring everyone up to date on Etch status: http://lists.debian.org/debian-devel-announce/200
Since its publication, Etch has gone into bug-fixing only.
Nice little bonus for debian users on the end if you read it all the way through.
Please, please
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
About the project being "frozen", I don't know about that. I have a laptop running etch-testing. I did an apt-get dist-upgrade in mid-Nov , put it away for a few weeks and ran it again in early-Dec (don't remember exact dates). Something like 70 packages needed upgrades.
Well, debian goes through a few stages of freeze. Base freeze was some time ago, general freeze was Dec 11th, but still there's something like 130 RC bugs that needs to be solved. I think the original plan called for something like 1.5mo of freeze, so probably sometime in January.
In any case, this is not what I call a big delay, it's maybe a month behind a release schedule of every 18 months, whereas the last took something like three years. 18 months is basicly the same as Ubuntu LTS and many other server oriented distros, if you want quicker updates go for (K)Ubuntu.
From what I gather the Debian system does a lot more than simply packing up whatever upstream does, but I think they could differentiate on levels of support. For non-server software I imagine that for many of the packages, there's no upstream support for so old versions anyway.
Live today, because you never know what tomorrow brings
Apt works with non-official repositories. What the parent wants is the official, default, debian sources to be slimmed down to something more managable, the main packages people use, while the rest of it can be set to third-party repositories that people can add in (or activate) as they need. Hell, they could be included in the sources.list file, just commented out until those who need them activate them (like Ubuntu does).
Debian ships When It's Ready.
But for those of us who are holding our breath for release time, a good and rough indicator of when it will ship is the number of release critical bugs. When the number hits zero, Debian is (almost?) ready. Since the etch freeze was announced about a week ago, the number of release bugs has wavered around 130, with a slight downward trend. This is the stock market of the free software world. :-) The etch freeze means that no packages can move down from unstable (sid) to the current testing (etch) automatically anymore (normally, packages in unstable are automatically moved down to testing by a script if no bugs are filed against them for some time, several days, iirc). Packages can still be moved from unstable to testing, but only manually if it's clear that they are stable enough for the next release.
The dunk-tank drama in the Debian mailing lists is old news. Yes, some developers expressed concerns about the dunc-tank project, but I would hardly call this "frozen development". Developers are working hard to get the Debian release. I estimate January or February at the latest will be beer and pizza party time for all the Debian developers that have produced the largest binary free GNU/Linux distribution amongst which so many other distros depend.
Personally, I'm very excited. I'm not sure how much truth there is in this, but Ubuntu has probably put pressure in Debian to more timely releases, and this release will be much more in time than the previous sarge release was. I've been given permission to install Debian in 20 workstations of our local network, and I'm waiting for the stable release and the renowned Debian quality and security to do so. I'll probably be tracking the next testing release after I install them, though, since testing works well for desktop use and workstations.
>That's one of the most self-righteous, idiotic statements I've ever heard.
...and being in the work force, you should know that often times people say "hey, I can cobble together some shit in five minutes and move on to the next thing I don't want to be doing".
NO U.
>You're saying that anybody who gets paid to do something does it for the money and doesn't care about the quality of what they do.
No, I'm saying that a lot of people would prefer that whoever is commiting to debian does so for the right reasons, and not because they're simply collecting a bounty.
>I get paid for most of what I do, but I take pride in my work.
So you're working in a stable and fulfilling job as opposed to collecting bounties on random projects then, I assume?
>If you had, you'd know that sometimes people have to say, "God, I'd love to work on that, but I need to be doing something that brings in some money."
> Many unpaid developers simply put off Debian work to work on something else.
...development is currently frozen.
This is a gross exaggeration.
>
This is false. Etch (Testing) is frozen in that packages are no longer automatically moving into it from Sid (Unstable) but this is a normal part of the release cycle: it happens just before a release. Development continues apace in Sid.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Well, actually, shelters that feed the poor and help battered women DO take donations to support the staff and the facility. Pretty much exactly what the folks paying the Debian guys were doing... put a little money in the pot so the facility can be open. So I'm afraid you came up with an example for the other side.
So you suggests that exists a lot of repositories instead of just add a repository with their three sections? I prefer one repository instead of a lot of them that I have to check if some of them fail, but if I have one I know wich one fails and can change it to another official repo that I know will works as I hope that work!
I don't want to add a diferent repository each time I want to install a new package... That sucks!
ghostbar page.
They call it `Ubuntu', and Debian persists because a bunch of people still want 15,000+ supported packages.
Yes, Ubuntu has {un,mult}iverse, but only *because* Debian continues to support those packages.
L
I call bullshit.
.dll files when you uninstall the app that it came with. The only exception is if something in the reg changed.
Have you EVER cleaned up your libraries? I'm fucking serious. Regardless of whether they're shared or not (and good luck with that one.)
Nobody keeps their house completely clean and the size of libraries is nothing compared to thee amount of pr0n or other shit on a hard drive.
Just STOP with the 'shared' library argument. One thing you can give Windows credit for is that it will even uninstall
But this old canard about Windows adding a library every time is horseshit. Let it die unless and until there's a decent package system that includes backing out old libraries. And no, 'checkinstall' doesn't cut it.
The opposite of progress is congress
They claim it's because they care about principle...in reality, what they really care about is retaining the ability to tell other people what to do and how to think.
Debian is one of the most flexible distributions availible. I don't give a rats arse about what some random Debian developer thinks about how I use my system or what programs I install because it doesn't affect me.
Personally I'd like to see Debian (as it currently exists organisationally) collapse entirely, and for the codebase to be adopted by Ubuntu, or other projects which will hopefully be run by people who are not so interested in dominating others.
How the hell is Debian collapsing going to help Ubuntu? Ubuntu already uses the Debian codebase. If anything Debian collapsing would hider Ubuntu. Your comment makes no sense.
IMO, this is a bad article. It's full of misinformation and factual errors, and it paints a very inaccurate picture of the current state of Debian.
From the article:
The date of Debian's first release given in this article is only one of the many factual errors that it contains. The Wikipedia article on Debian ( http://en.wikipedia.org/wiki/Debian ) tells that "The Debian distribution was first announced on August 16, 1993 by Ian Murdock" and "The Debian Project grew slowly at first and released its first 0.9x versions in 1994 and 1995." Debian version 1.1 was released in June 1996, version 1.2 in December 1996, and version 1.3 in June 1997.
Of course, the article also fails to mention that the Ubuntu distribution is based on Debian and Ubuntu's each new release relies heavily on the work that is constantly being done in Debian, and the article also fails to tell that Ubuntu takes most of the code it releases from Debian's development branch.
http://mako.cc/writing/to_fork_or_not_to_fork.html
From the article:
Actually, there's no factual evidence at all that the delay in Debian's release schedule is caused by developers doing their work slower than usual. It is not easy to grasp how large and complex the Debian project has grown and many journalists also obviously fail to understand the not-for-profit and volunteer nature of the work that is done in Debian. The huge size of the project and the volunteer nature of its work are sufficient reasons alone to explain why the release has been delayed for a month or two. Such delays can happen for purely organizational reasons even if every developer is working as hard as they can.
Debian is a non-profit volunteer organization where all the important decisions are made democratically. ( http://en.wikipedia.org/wiki/Democracy ) This means that all important issues in the project management are openly discussed over a period of time and every developer has a chance to get their voice heard. From time to time there are disagreements among the developers and these disagreements are settled by voting where the opinion of the majority wins.
There was recently some disagreement among the Debian Developers about the experimental idea to fund two release managers' full-time work for a short period of time just before the upcoming Debian release. The Debian Developers voted about this issue and the majority of them decided to support the experiment. ( http://lists.debian.org/debian-devel-announce/2006 /10/msg00019.html ) Most of the developers accepted this result but 17 of them have been protesting even after the results of the voting were published. It is perhaps worth mentioning here that Debian has over one thousand officially accepted developers and many more who contribute to the project without having the official developer status. 17 developers out of 1000 is a small minority but they can still make a lot of noise. Those other developers concentrate on coding instead of public arguing, so it is only too easy for the scandal-hungry journalists to ignore all these hard-working silent developers and concentrate on the loud complainers.
http://lists.debian.org/debian-devel-announce/2006 /10/msg00026.html