Language Selection

English French German Italian Portuguese Spanish

Always-Releasable Debian Means Shorter Waits

Filed under
Linux

It took nearly two years for Debian 7.0 to reach the masses. Wirzenius and co-writer Russ Allbery (Debian hacker) say a big portion of that was eaten up by the 10-month freeze, which just stressed everyone out. Wheezy's freeze was four months longer than past releases and at that Wirzenius feels they are too long. He says, "We should aim for a short freeze, perhaps as short as two weeks, and certainly not longer than two months." But an "always releasable" Debian would require some big changes.

Wirzenius says the first thing that needs to change is their attitudes. He says everyone needs to take ownership of releases, not just the release team and realize that releases are important. He thinks testing should be kept free of RC bugs and use automatic testing more.

rest here




More in Tux Machines

OSS Leftovers

  • The Future of Marketing Technology Is Headed for an Open-Source Revolution
  • Edging Closer – ODS Sydney
    Despite the fact that OpenStack’s mission statement has not fundamentally changed since the inception of the project in 2010, we have found many different interpretations of the technology through the years. One of them was that OpenStack would be an all-inclusive anything-as-a-service, in a striking parallel to the many different definitions the “cloud” assumed at the time. At the OpenStack Developer Summit in Sydney, we found a project that is returning to its roots: scalable Infrastructure-as-a-Service. It turns out, that resonates well with its user base.
  • Firefox Quantum Now Available on openSUSE Tumbleweed, Linux 4.14 Coming Soon
    Users of the openSUSE Tumbleweed rolling operating system can now update their computers to the latest and greatest Firefox Quantum web browser.
  • Short Delay with WordPress 4.9
    You may have heard WordPress 4.9 is out. While this seems a good improvement over 4.8, it has a new editor that uses codemirror.  So what’s the problem? Well, inside codemirror is jshint and this has that idiotic no evil license. I think this was added in by WordPress, not codemirror itself. So basically WordPress 4.9 has a file, or actually a tiny part of a file that is non-free.  I’ll now have to delay the update of WordPress to hack that piece out, which probably means removing the javascript linter. Not ideal but that’s the way things go.

Red Hat and Fedora Leftovers

Darling ('Wine' for OS X) and Games Leftovers

Linux 4.13.14, 4.9.63, 4.4.99, and 3.18.82