Slashdot Mirror


Debian Decides To Adopt Time-Based Release Freezes

frenchbedroom writes "The ongoing Debconf 9 meeting in Cáceres, Spain has brought a significant change to Debian's project management. The Debian project will now freeze development in December of every odd year, which means we can expect a new Debian release in the spring of every even year, starting with 'Squeeze' in 2010. Until now, development freezing was decided by the Debian release team. From the announcement: 'The project chose December as a suitable freeze date since spring releases proved successful for the releases of Debian GNU/Linux 4.0 (codenamed "Etch") and Debian GNU/Linux 5.0 ("Lenny"). Time-based freezes will allow the Debian Project to blend the predictability of time based releases with its well established policy of feature based releases. The new freeze policy will provide better predictability of releases for users of the Debian distribution, and also allow Debian developers to do better long-term planning. A two-year release cycle will give more time for disruptive changes, reducing inconveniences caused for users. Having predictable freezes should also reduce overall freeze time.' We previously discussed talks between Canonical and the Debian release team about fixed freeze dates."

21 of 79 comments (clear)

  1. Linux: Debian by BadAnalogyGuy · · Score: 3, Insightful

    Two things to note.

    First, the small font used for the non-mainpage stories makes me read the story title as "Lesbian decides to adopt time-based release freezes".

    Second, limiting an OSS project to a time-based release cycle puts an artificial constraint on the development process. While it might be useful to encourage faster development in some cases, it is just as likely to force a new feature to be dropped at the last minute if it can't make it through the door in time.

    I'd rather they stick with feature-based releases which focus on the quality of features rather than trying to force feature development into a specific duration.

    1. Re:Linux: Debian by nosfucious · · Score: 4, Interesting

      And refering to Spring/Winter is too imprecise. It's currently (July) Winter in the Southern Hemisphere.

      Try refering to Quarter 1, Quatert 4, etc for times of the year.

      However nit picking aside, at least we shall now get some certainty in the releases of (probably) the worlds best distro.

      8-)

      --
      Q:I was listening to a CD in Grip and it sounded horrible! What's up? A:Perhaps you are listening to country music
    2. Re:Linux: Debian by Anonymous Coward · · Score: 5, Funny

      a.) It says December, I'm pretty sure December is always in December no matter what hemisphere you're in, which makes it pretty obvious what they mean by Spring.
      b.) No one cares about the Southern Hemisphere.

    3. Re:Linux: Debian by TREE · · Score: 5, Insightful

      No schedule, feature based or time based, will have all upstream developers in sync. Someone will always be developing new stuff and want to squeeze it in.

      At least this way, there's a known target that developers can be (made) aware of.

    4. Re:Linux: Debian by lenzm · · Score: 2, Insightful

      All releases are artificial constraints. There's always new features that could be included.

    5. Re:Linux: Debian by lordandmaker · · Score: 2, Funny

      The release in the Southern Hemisphere has an extra six-months of bug squishing.

    6. Re:Linux: Debian by noundi · · Score: 2, Interesting

      Second, limiting an OSS project to a time-based release cycle puts an artificial constraint on the development process. While it might be useful to encourage faster development in some cases, it is just as likely to force a new feature to be dropped at the last minute if it can't make it through the door in time.

      At the same time a release can be delayed for the opposite reason and you end up delaying the entire project due to some packages.

      The trick to avoiding your scenario and my scenario is by carefully picking the most appropriate intervals. Not too long between as this will drag out development leaving already stable and wanted features on hold for a longer time than necessary, and not too short leaving unstable features dropped or hurried out. The best way to do this would be to categorize your packages in different priorities, then gathering all the most important packages and calculating a suitable interval spectrum which is then used as the foundation for choosing the exact dates after having reviewed the less critical packages. Of course this won't please "everybody", but there is no solution for that. The only possibility is to please "as many as possible" in relation to their importance. To make it clear I'm personifying software packages when I refer to them as "everybody" and "as many as possible".

      --
      I am the lawn!
    7. Re:Linux: Debian by clang_jangle · · Score: 3, Interesting

      ...limiting an OSS project to a time-based release cycle puts an artificial constraint on the development process. While it might be useful to encourage faster development in some cases, it is just as likely to force a new feature to be dropped at the last minute if it can't make it through the door in time.

      I definitely agree, however I expect this decision was driven by concerns that Debian's popularity with businesses might be threatened by Ubuntu. Pointy-haired types like to see "regular" release schedules, rather than "we'll release it when it's done".

      ...the small font used for the non-mainpage stories makes me read the story title as "Lesbian decides to adopt time-based release freezes".

      You might want to revisit your browser's font configuration then. I certainly would never depend on the font choices of web designers. :)

      --
      Caveat Utilitor
    8. Re:Linux: Debian by AlXtreme · · Score: 2, Insightful

      I like Debian's commitment to free software, but if you don't deliver a product people will look elsewhere.

      They did and do deliver a product: a rock-solid stable Linux distribution.

      Some people care more about a stable environment (for servers or workstations) than the latest bells and whistles. That, together with the necessary security fixes, makes Debian the best distribution for me hands-down. And if you run Ubuntu or any derivative, you're still running Debian under the hood. Even if you don't need a rock-solid distribution, they allow other groups to give you those bells and whistles you want.

      Rather than whine about those 3 years (hell, if you really needed an upgrade you could have tried out testing), be grateful that there are so many people out there that put this distribution together in their spare time and by doing so make your distribution possible.

      --
      This sig is intentionally left blank
  2. Previous way by sleekware · · Score: 3, Interesting

    I've always liked Debian's way of doing their releases, it was unique and worked really well for them for awhile; I hope this new way works out for the best and mutually benefits both Debian and Ubuntu.

  3. I like this by tayhimself · · Score: 2, Interesting
    This is almost like an Ubuntu LTS release? I am very happy with Ubuntu LTS for my servers. I think this is a step in the right direction for debian, but I don't see why I would go with a Debian server as opposed to an Ubuntu one.

    Still thank you to the debian team for we depend on their hard work.

    1. Re:I like this by lordandmaker · · Score: 4, Informative

      Er, ish.

      Debian Stable is the closest Debian has to an equivalent of Ubuntu's LTS release. Debian Testing's about a Ubuntu 'normal'.

      But the two distros work in different ways, the comparison's not that cut-and-dried, since LTS releases are just normal releases with long support times.

      Debian Stable is unchanging in featureset for its lifetime, Debian Testing is the testing for the next Stable, and Debian Unstable is where the changes to be tested are made.

      As I understand it, Ubuntu 'freezes' a mirror of Debian testing, prettifies it, and releases it as Ubuntu. This is grossly under-representing Ubuntu's contribution, but is sort-of accurate in principle

    2. Re:I like this by Nursie · · Score: 2, Informative

      Well, I likewise don't see why you would go for an ubuntu server over a debian one :)

      Ubuntu has a six monthly release cycle with yearly LTS IIRC?

      Debian is effectively always LTS, when it's released. When you release every two years and provide patches and updates for the oldstable as well as the stable branch you effectively have a 4 year support cycle anyway.

      Also, Ubuntu is *so* x86 and whilst I know this is changing slowly I have three headless ARM based servers running debian right now. Err...
      For me, Ubuntu didn't get on very well with my laptop and debian does. YMMV, obviously, and we've strayed out of serverland now. I know Ubuntu has advantages, but debian is my distro of choice.

  4. Re:By the Way - this insane versioning bent by lordandmaker · · Score: 5, Informative

    But sit down at a random machine and try work out WHAT release of Debian (or Fedora or whatever) you are actually sitting in front of and you can pull your hair out.

    cat /etc/issue
    cat /etc/apt/sources.list
    cat /etc/lsb_release

    Often works. It's by no means ubiquitous, I'm well aware, but it's rarely *that* difficult.

  5. Re:By the Way - this insane versioning bent by PieSquared · · Score: 2, Informative

    Ubuntu does reasonably well with this. They get the catchy name *and* obvious order by coming up with names associated with a letter, in alphabetical order. Jaunty is more recent then Feisty because "J" comes after "F".

    And then they also stick the month and year on as the version number, which I thought was a good idea. 9.04 Jaunty is more recent then 7.04 Feisty because "J" comes after "F" and "April 2009" comes after "April 2007".

    And finally you get an "about" page that lists both the name and the number.

    --
    Does a line appended to your comment give your post meaning in and of itself, or only in relation to those without?
  6. Re:By the Way - this insane versioning bent by archen · · Score: 5, Funny

    Seeing as how debian only releases every century or so, that's not really a problem. The current release is the one you hear about. If it's not that it's the one you vaguely remember. The one before your kids were born, you were in high school, or possibly back when MTV played music videos (or insert some other thing waay back). If it's a version you haven't heard of it's so outdated that only the old long bearded unix sages locked up in corporate server farms programing cobol/fortran remember much about.

  7. Nothing personal, just a different opinion by zsau · · Score: 4, Insightful

    I run Debian stable on my laptop, and I don't see why I would run Ubuntu instead of Debian. Debian has a larger range of packages and is much more flexible and forgiving if you don't want to run one of the preconfigured subdistros (i.e. Ubuntu/Gnome, Kubuntu, Xubuntu etc.). Plus, having run distributions like Debian/sid or Gentoo, which have continuous updates, I find the reliability you get from a computer which never randomly changes packages is a plus. The six-monthly timetable of Ubuntu is much too short for that; I would've got the bugs ironed out just in time for a new release. There is, as you indicate, the LTS releases: but they're just one of the regular releases and this means you get people pulling in opposite directions (latest and greatest vs good for the whole three/five years). Also, is there some guarantee that you can always upgrade from one LTS release to the next LTS release?

    In short, with Debian stable, I know what I'm getting. With Ubuntu, in my mind there's too much uncertainty that I'll have a reliable computer for its lifespan. Even if there isn't any uncertainty, there's no reason to convert. No matter how good Ubuntu is, I can't imagine it being better enough than Debian (on my desktop for my purposes) to warrant converting.

    (That said, I would like answers to my questions. Googling "Ubuntu LTS" gives you almost nothing about LTS in general. The one page that's not information about a specific release has almost no content: a paragraph about Ubuntu's normal release schedule, a paragraph about the LTS release schedule, and a paragraph taking you to a list of pages about the beta releases (!) of distributions released a year (!!) or three (!!!) ago. This absence of information, and absence of relevant information, fills me with an absence of confidence, and it's one reason I'm not going to switch my laptop from Debian stable.)

    --
    Look out!
  8. Re:By the Way - this insane versioning bent by Anonymous Coward · · Score: 4, Informative

    For Debian based systems:
     
    cat /etc/debian_version

  9. Re:By the Way - this insane versioning bent by zsau · · Score: 2, Funny

    You should probably get your centuries looked at, if you're only getting around two years out of them. Mine last a hundred years or so; I gather that's about average.

    --
    Look out!
  10. Re:By the Way - this insane versioning bent by arjennienhuis · · Score: 3, Informative

    lsb_release -a

  11. Re:By the Way - this insane versioning bent by Sophacles · · Score: 2, Insightful

    The debian page itself lists releases by number and code name. So does Mac OS X, of course they are all referred to by code name too, leopard, tiger, etc. The Windows world has it easy, Windows 7 comes after windows 95, as per standard numbering schemes. Don't forget that in number based versioning schemes 2.1 is different than 2.10, and that 2.1 is before 2.9, which in turn is before 2.10. In debian of course you could just replace codenames with stable, testing and unstable and be done with it.

    --
    To live till you die is to live long enough. -Lao Tzu, Tao Te Ching