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

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!