Ubuntu considers switch to a rolling release model between LTS editions


Recommended Posts

Ubuntu considers ?huge? change that would end traditional release cycle

Ubuntu 12.10 (thus named because it came out in October 2012) has just arrived, and 13.04 and 13.10 will come in April and October of 2013. But 14.04 in April 2014 could be the last version released after just a six-month development period. 14.04 is also the next "Long Term Support" or LTS edition. Every two years, Ubuntu is sort of frozen in place with a more stable edition that is guaranteed support for five years. If the change Canonical is considering is adopted, every future edition starting with 14.04 will be an LTS, so the next version after 14.04 would be 16.04 in April 2016.

Why bother? Canonical kernel team manager Leann Ogasawara explained in a Google hangout today that this proposal is on the table because Canonical thinks it can deliver both stability and cutting-edge features with rolling releases. For the two years between LTS releases, there would be no new versions but there would be lots of updates.

Read more

Why bother? Canonical kernel team manager Leann Ogasawara explained in a Google hangout today that this proposal is on the table because Canonical thinks it can deliver both stability and cutting-edge features with rolling releases.

Oh cahoot, does that mean thorough testing and coding of any changes they make before actually implementing them and forcing them on users, if so; microsoft, arch linux team, nokia, et al. please take note.

This could be a good idea, the 6 month release cycle has become pretty outdated IMO. The non-lts releases have always been glorified betas, so they might as well just go rolling release between the LTS releases. I really like the sound of this.

Could it ever truly be rolling if debian is not rolling?

Debian has (or at least had last time I messed with it) a rolling branch, unstable (Sid).

http://wiki.debian.org/DebianUnstable#Introduction

Several distros like Bodhi Linux do a semi-rolling release where they update the software but only update the system when they get system updates from Ubuntu. They are based on 12.04.1 currently. I would be happy with something like that, with only security updates coming down the line.

Several distros like Bodhi Linux do a semi-rolling release where they update the software but only update the system when they get system updates from Ubuntu.

Yea Chakra's doing this too (via Arch).. the core system is released in 'stages' or however you want to word it, the applications themselves (stuff that won't kersplode your system) is rolling. Actually a pretty good setup I think.. system's stable yet you're constantly up to date with the "regular" software.. in theory the worst that'll happen is the one application will crash, no more "holy god what did I do" moments with an update. Arch had a few major doozies if you weren't paying attention to their news feeds and what the updater is doing.

My apologies, I thought unstable was not rolling.

You are actually correct. Sid is not rolling. It is never technically put into freeze like Testing before release, but since Unstable's main purpose is to act as a staging area for Testing, it is effectively frozen at the same time as Testing. Unstable may have slightly newer versions of some packages during a freeze, or even packages that were removed from Testing because they were deemed too unstable or buggy for release, but no major new software versions are introduced. (For example, GNOME 3.4 is in both Sid and Wheezy even though GNOME 3.6 is considered stable upstream.) Once Wheezy is released, Sid will be forked to become the basis for Jesse, then it will effectively be unfrozen.

There are actually several proposals to create a truly rolling branch of Debian that are often brought up around release time. The consensus, at the moment at least, seems to be that creating a rolling release would distract developers from fixing release-critical bugs - thus preventing Testing from being released in a timely manner - and generally reduce the quality of Debian as a whole.

Canonical might be able to pull off a rolling release of Ubuntu with some software that they maintain internally, such as Unity or the Linux kernel, but they don't have the resources to independently maintain every package in the Debian archive. I think that their "rolling release" will focus mainly on a few key packages that Canonical themselves maintain, and the remainder will be maintained by regular imports from Sid. Effectively, Ubuntu's rolling release will semi-freeze the same way Sid does, though possibly to a lesser extent, when Debian freezes Testing. The only practical way around that limitation would be for Debian to create a true rolling-release branch, which isn't likely to happen, or Canonical to re-base on another distribution, which is even less likely to happen.

Debian in my opinion has a slighty different Market to Ubuntu, "rolling release" and "stable" does not always go well hand in hand.

I completely agree. I'm definitely against Debian adding a rolling-release repository. Fortunately, it seems that the vast majority of Debian Developers agree with me.

Canonical, on the other hand, might be able to pull it off. My last post might have made it sound a little like I'm against Ubuntu becoming a rolling distribution: I'm not. I merely pointed out some of the challenges they will face making that happen. That said, I'm sure they've thought it through.

I've seen some nods from the Fedora camp that they may move into rolling releases, or at least offer both stable releases and a rolling release. They currently have something like that (rawhide) but it's not an official rolling release.

Based on my experience with Arch on a pogoplug, rolling releases need to be improved a bit but there is a lot of promise there as long as they roll smoother than a square tire.

And I'd greatly like a more frequently updated DE.

Now I based my information on distrowatch and I understand the time between today and the rolling release but it is my opinion that the stability / cutting edge mixture they have currently adopted (and usability) is what brought Ubuntu to the fore-front of popularity.

The Ubuntu distro losing popularity and I am sure many have opinions why - changing the release strategy might not be the move to reverse the path they are on.

Perhaps current adopters might have a fluctuation but the "windows" converts will be further distanced and for those who are looking for a "light" distro may leave.

This is a wild statement but I have always felt that Ubuntu provided the strengths of Linux without the feel and complexity.

This is not to say Ubuntu is limiting - clearly it can be used by hardcore / new comers a like.

To back step a little I missed the fact LTS releases will sexist but I would still expect on some level windows converts will be entangled with this concept of "most recent release" and the expectation of everything being close to perfect.

good idea imho. and in the meantime i just use fuduntu, as it is a rolling release plus combines the best of ubuntu and fedora.

Now I based my information on distrowatch and I understand the time between today and the rolling release but it is my opinion that the stability / cutting edge mixture they have currently adopted (and usability) is what brought Ubuntu to the fore-front of popularity.

The Ubuntu distro losing popularity and I am sure many have opinions why - changing the release strategy might not be the move to reverse the path they are on.

I don't think Ubuntu cares about the desktop anymore. They are more focused on mobile now.

I don't think Ubuntu cares about the desktop anymore. They are more focused on mobile now.

To be fair Ubuntu has been looking to spread itself around in all sorts of already heavily dominated markets.

This topic is now closed to further replies.
  • Posts

    • In what way is any of what I said incorrect? To install an update you need to close all browser instances, upping it from once a month to once a fortnight is an inconvenience for users. Particularly when updates don't offer functionality that users want (notably copilot). Security updates should come as they are needed, not on a release schedule
    • Dopamine 3.0.6 by Razvan Serea Dopamine is an awesome free audio player which tries to make organizing and listening to music as simple and pretty as possible. Dopamine has been designed for Windows 7, Windows 8.x and Windows 10 and plays mp3, ogg vorbis, flac, wma and m4a/aac music formats quite well. The best part? It's created by long-time Neowin member, Raphaël Godart. If you’re looking for a music player to handle a large music collection, you should definitely give Dopamine a try. Dopamine 3.0.6 changelog: Fixed Manually edited album covers are overwritten on the next collection refresh Fixed AppImage package not working on modern GNU/Linux distributions Deleting song from playlist sometimes fails Playback controls only work when clicking on upper half of the buttons It's unclear that files must be tagged with an external ReplayGain scanner (for example rsgain) before normalization can take effect. Change to Artist or Album tags is not reflected in the song list view nor in the Now Playing information ReplayGain issues Smart playlist filters ignore text containing accents or other special characters Some MP3 files trigger an "MPEG header not found" error due to a too-narrow initial MPEG header scan range Changed Updated the Vietnamese translation Download: Dopamine 3.0.6 | 122.0 MB (Open Source) Links: Home Page | Forum Discussion | Screenshot | Other OSes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • BleachBit 6.0.1 Beta by Razvan Serea When your computer is getting full, BleachBit quickly frees disk space. When your information is only your business, BleachBit guards your privacy. With BleachBit you can free cache, delete cookies, clear Internet history, shred temporary files, delete logs, and discard junk you didn't know was there. Designed for Linux and Windows systems, it wipes clean thousands of applications including Firefox, Microsoft Edge, Google Chrome, Opera, Safari, and more. Beyond simply deleting files, BleachBit includes advanced features such as shredding files to prevent recovery, wiping free disk space to hide traces of files deleted by other applications, and vacuuming Firefox to make it faster. Better than free, BleachBit is open source. BleachBit has many useful features: Delete your private files so completely that "even God can't read them" according to South Carolina Representative Trey Gowdy. Simple operation: read the descriptions, check the boxes you want, click preview, and click delete. Multi-platform: Linux and Windows Free of charge and no money trail Free to share, learn, and modify (open source) No adware, spyware, malware, browser toolbars, or "value-added software" Translated to 64 languages besides American English Shred files to hide their contents and prevent data recovery Shred any file (such as a spreadsheet on your desktop) Overwrite free disk space to hide previously deleted files Portable app for Windows: run without installation Command line interface for scripting and automation CleanerML allows anyone to write a new cleaner using XML Automatically import and update winapp2.ini cleaner files (a separate download) giving Windows users access to 2500+ additional cleaners Frequent software updates with new features Going beyond standard deletion of files, BleachBit has several advanced cleaners: Clear the memory and swap on Linux Delete broken shortcuts on Linux Delete the Firefox URL history without deleting the whole file—with optional shredding Delete Linux localizations: delete languages you don't use. More powerful than localepurge and available on more Linux distributions. Clean APT for Debian, Ubuntu, Kubuntu, Xubuntu, and Linux Mint Find widely-scattered junk such as Thumbs.db and .DS_Store files. Execute yum clean for CentOS, Fedora, and Red Hat to remove cached package data Delete Windows registry keys—often where MRU (most recently used) lists are stored Delete the OpenOffice.org recent documents list without deleting the whole Common.xcu file Overwrite free disk space to hide previously files Vacuum Firefox, Google Chrome, Liferea, Thunderbird, and Yum databases: shrink files without removing data to save space and improve speed Surgically remove private information from .ini and JSON configuration files and SQLite3 databases without deleting the whole file Overwrite data in SQLite3 before deleting it to prevent recovery (optional) BleachBit 6.0.1 Beta release notes: BleachBit 6.0.1 beta is now available for testing. This maintenance-focused release includes bug fixes, updated translations, and a range of safe enhancements. This release fixes a Windows security issue that could allow arbitrary file deletion during privileged cleaning (reported by Zeze with TeamT5). It also adds new cleaners (including a DNS cache cleaner, Claude Code, and Visual Studio Code forks), support for multiple Chrome and Edge profiles, new deep scan options for developer directories like node_modules and venv, and safer, faster file shredding. All Platforms Added cleaners for Claude Code, DNS cache, and many Visual Studio Code forks. Added support for multiple Chrome and Edge profiles. Chrome can now clean downloaded AI models. Deep Scan can optionally remove venv, __pycache__, node_modules, and .angular directories. Deep Scan is faster by skipping directories on the keep list. File shredding is safer, faster, and leaves fewer recoverable traces. Improved handling of cookies, symlinks, Unicode filenames, external processes, and configuration files. Improved Expert Mode warnings and long warning dialogs. Fixed crashes related to cleaner detection, invalid Unicode, and malformed cleaner data. Clipboard is now cleared automatically after shredding files via paste operations. Linux Added AppImage support. Added cleaners for Visual Studio Code, Codeium, Librewolf (.deb), Transmission (Flatpak), and Profanity. Improved Linux trash detection, including Snap-installed applications and mounted drives. Fixed Wayland root CLI issues and several Snap-related problems. Improved package dependencies, AppStream metadata, and desktop file handling. Fixed startup crashes when Python Requests is unavailable. Windows Fixed a security vulnerability that could allow arbitrary file deletion when cleaning with elevated privileges. Added %WindowsSystem% variable support. Improved clipboard clearing using native Windows APIs. Improved installer experience on unsupported Windows versions. Reduced installer size and improved application robustness. Fixed Unicode handling, filename anonymization, Git revision reporting, and splash screen stability. [full release notes] Download: BleachBit 6.0 | Portable | ~20.0 MB (Open Source) View: BleachBit Home page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
    • Week One Done
      ssd21345 earned a badge
      Week One Done
    • Contributor
      MarkHughes4096 went up a rank
      Contributor
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      193
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      96
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!