Stories
Slash Boxes
Comments
Search

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Anthony Towns Elected New Debian Leader

Posted by ScuttleMonkey on Mon Apr 10, 2006 07:14 AM
from the there's-a-new-sheriff-in-town dept.
Debian Software Linux
daria42 writes "Australian developer Anthony Towns has just been elected Debian Project Leader starting 17 April. In his platform for election, Towns said the most important issue for Debian was 'increasing its tempo'. 'We've been slow in a lot of things, from releasing, to getting updates in, to processing applications from prospective developers, to fixing bugs, to making decisions on policy questions, and all sorts of other things,' he said."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Anthony Towns Elected New Debian Leader 25 Comments More /

 Full
 Abbreviated
 Hidden
More
Loading... please wait.

  • Slowness (Score:5, Funny)

    by CRCulver (715279) <crculver@christopherculver.com> on Monday April 10 2006, @07:19AM (#15098205) Homepage
    As the old saying goes, "Hell freezes faster than Debian Stable". Good to see that Towns intends to take action.
    • As the old saying goes, "Hell freezes faster than Debian Stable". Good to see that Towns intends to take action.

      The three main BSD projects are comparable to Debian, yet they manage to get their releases out on a (fairly) regular basis.

        • The only one I have any experience with is FreeBSD, and I can say for a fact that I would never dream of using an X.0 release of FreeBSD. Since I've started following their progress, it's always taken till at least X.4 before a major version was stable enough to consider for serious use.

          OpenBSD has a different release policy (i.e. a release every six months) that works very well. The 3.9 release is coming 1th of May, but the release in November will have version 4.0. Of course, someone had to ask if 4.0

            • So for OpenBSD this means that they have working installer, you can compile your own kernel on your own box and most of the basic tools exist (emphasis mine.)

              It's requirement for a supported arch that not only the kernel, but userland (including thirdparty applications like perl, Apache httpd, BIND, Sendmail, gcc toolchain and more) must also be built natively: cross-compiling is not sufficient to claim support, unlike some other OS that shall be unnamed. Some archs, like vax, is limited by hardware, wh

  • Joke (Score:5, Funny)

    by zaguar (881743) on Monday April 10 2006, @07:28AM (#15098220)
    For those who were wondering, voting started in 2001. He was elected today because the commitee wanted to make sure the candidates were 'stable'.

    • Re:Joke (Score:5, Funny)

      by wild_berry (448019) on Monday April 10 2006, @07:45AM (#15098255) Journal
      You forgot to mention that the candidates were also frozen for bugfixing. Towns has only lost two fingers to frostbite; the debian-privates e-mail list suggests that another candidate lost something more personal and delicate.
    • For those who were wondering, voting started in 2001. He was elected today because the commitee wanted to make sure the candidates were 'stable'.

      If we had only used that method in choose the current US President ...

  • there's-a-new-sheriff-in-town dept.

    I can see I'm not the only one who read that as, "Anthony Debian Elected New Town Leader."

    -Loyal

  • Brandon replaced after only 1 year? (Score:4, Interesting)

    by JSBiff (87824) on Monday April 10 2006, @09:48AM (#15098612) Journal
    I don't really follow Debian politics much. But, I remember seeing just last year that Brandon Robinson had been elected project lead (he too was planning to put Debian on a faster release cycle last year as I recall).

    So, did Brandon resign the post, or did the Debian voters just decide that 1 year of Brandon was enough? I presume that Debian must elect a new leader annually? Are incumbents allowed to run for a second term? Did Brandon run again? Can anyone provide a post-mortem of Brandon's year - was it generally considered that he did a good job in the post?

    • Re:Good Move (Score:4, Insightful)

      by babbling (952366) on Monday April 10 2006, @07:31AM (#15098228)
      What makes you think that? I mean, sure, he stated that he wants to get releases out quicker, but that doesn't necessarily mean he will be able to. I imagine that has more to do with the independent, unpaid Debian developers rather than the project leader. It's rather likely that the previous Debian project leader also wanted a shorter release cycle.

      This is one of the problems with free software. If developers are less accountable, fixed release dates are more difficult to achieve. On the other hand, almost all proprietary software seems to be facing the same problem, and sometimes to a greater degree...
      • I think the slowness of Debian has a lot to do with the endless discussions, too. I don't say they're irrelevant or obsolete but they can get very lengthy (and sometimes repetitive) on some topics. In effect some decicions take longer than expected and schedule's getting out of control. Nevertheless, I'm a happy Debian user.
        • I'm a happy Debian user, too. I just thought I should point out that a leader who wants quicker release cycles doesn't necessarily imply quicker release cycles.
      • What makes you think that? I mean, sure, he stated that he wants to get releases out quicker, but that doesn't necessarily mean he will be able to. I imagine that has more to do with the independent, unpaid Debian developers rather than the project leader.

        Unlike the equally unpaid Gentoo Developers who manage to make 2 releases every year, and at point even did 4 (but that was, i admit, too much work).

      • Best intentions... (Score:4, Insightful)

        by QuaintRealist (905302) * <quaintrealist.gmail@com> on Monday April 10 2006, @09:01AM (#15098458) Homepage Journal
        I'd have to agree with you. One of the main reasons Debian has been slow to update has been the range of architectures and applications they attempt to simultaneously support. Other distros update faster, but most of them take one of two paths: a) limit supported architecture (usually to the x86 and x86 64) or b) support only a small subset of applications.

        Really, as much as I'd love to see Debian update faster, I'd hate to see them take one of those expediencies to get the job done.
        • The reason why Gentoo can release predictably and why Debian can't is that Gentoo allows
          different profiles for different architectures (Gentoo 2006.0 may have different stable versions for an app for different architectures, assuming the app is available for both
          arches in the first place) while Debian requires that the stable profile for each arch is
          synchronized.

    • Re:Debian (Score:5, Insightful)

      by lpcustom (579886) on Monday April 10 2006, @08:36AM (#15098383)
      I have to disagree totally. Ubuntu does have newer software for it's main distro. Debian Testing has just as new software cept it works better. For example, Ubuntu is still using firefox 1.0.7. Debian testing is at 1.5. Ubuntu's latest dapper flights are basically Debian Testing with new artwork that says Ubuntu.
      I like a ton of distros but I seem to always come back to Debian. For a bunch of guys that can't get their act together, they still make the others looks bad.

      • Re:Debian (Score:3, Interesting)

        by Arkaein (264614)
        I disagree that Debian Testing's packages work better than Ubuntu (or at least Kubuntu, in my case). I used Debian Testing for nearly two years, but late last year I decided to give Kubuntu a shot and haven't looked back. The final straw was a large set of KDE updates. I had a version of Amarok that I believe was either broken or had some key bug that was fixed in more current versions, but due to some kind of broken dependency chain in Debian Testing there was no way to upgrade anything KDE related. It was

    • Worst idea ever? (Score:5, Insightful)

      by babbling (952366) on Monday April 10 2006, @09:20AM (#15098516)
      Why? I'm a Debian user, and I appreciate how well EVERYTHING works. I'd hate for them to sacrifice the quality of most of the software I use just so they can release twice as often.

      I don't really trust distributions that guarantee a release every 6 months, because I get the impression they must be rushing things. I'd prefer something quality, even if it's usually "behind the pack".
      • It's not rushing if you work off a small core (see OpenBSD). I would rather have a really stable up-to-date system than 1000's of packages I don't use.

        They just can't make everything work stable when there are thousands upon thousands of packages, that's why it takes so long to release anything. In the meantime we're stuck with either an incredibly outdated system or running the unstable branch that changes way too often and sometimes breaks (not good for servers or media boxes and similar).

      • Why? I'm a Debian user, and I appreciate how well EVERYTHING works. I'd hate for them to sacrifice the quality of most of the software I use just so they can release twice as often.

        The idea isn't to skip testing, the idea is to decouple the release schedule of the OS from the release schedule of the applications. So long as the base Debian system maintains compatibility between releases (and I was under the impression it did), it shouldn't matter to the applications when new versions of the OS is rel

      • More to the point, I'd hate for them to release twice as often period. I maintain more than 60 machines; frequent release upgrades would be a serious drain on my time.

        If you want a distro that does significant upgrades to core packages every few weeks, get Fedora. Its great for that. Sucks for stability, but it has a really fast upgrade cycle.

      • Re:Worst idea ever? (Score:4, Informative)

        by croddy (659025) on Monday April 10 2006, @10:25AM (#15098747)
        I would definitely agree. It is unusual (in the Linux world) that Sarge took two and a half years to release, but I think that the benefits of the Debian QA process are very apparent. Taking the time to sort out bugs as well as they do -- on a very large number of packages -- makes a Debian release worth waiting for.

        The slower release cycle is offset by two things. If you know you need a fresher system, and are willing to sacrifice some stability for updated packages, you have as many choices as you can handle: adding a few packages from testing to your stable system, directly tracking testing or unstable, some mix of any of the three, or even adding packages from experimental if you really want to go out on a limb.

        The power of Debian is not only in APT, but in Debconf, the configuration system. Configuration changes are pretty much a given on a system that's directly tracking sid, but are unheard-of (and perhaps even forbidden?) in the stable release. The ease of administration that comes with knowing that changes Debian stable will consist only of backported security patches makes it worth the wait.

        Lastly, a system administrator does not want to have to go through a major operating system upgrade on numerous heterogenous servers every 9 months. Knowing that it will be somewhere around 18-36 months between Debian releases means spending a lot less time migrating and fiddling with systems just to keep up with supported releases.

        Other distributions do release every 6-9 months. It's not for me... except when it is, and I use testing/unstable in those cases :-)

    • I value their large repository for its well-organized dependency tracking and the fact that packages have all been tested for mutual compatibility.

      I don't care how often "stable" releases. I track "testing" with frequent dist-upgrades on my desktop machines, and on servers I'd not worry if "stable" was a bit long in the tooth.

      Throwing away the packages to get a rapid release cycle would be a bad bargain for me.

All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2009 Geeknet, Inc.