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

    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
    • So how did you solve the problem? Disabling Secure Boot isn’t a solution.
    • Another devilish issue surrounding these certificates is what can happen with old, unsuspecting PCs that nevertheless have Secure Boot enabled. In my case, it was a Dell with a 3rd-gen Core chip (so about 13 years old). As of the last few weeks, it was suddenly BSOD'g within about 5 minutes of booting. Turns out it was because of MS's "Secure-Boot-Update" scheduled task, which is scheduled to run 5 minutes after login. It's explained in gory detail here (this is not my post, but it was where I found the answer), but the short version is that this legacy system would need fairly elaborate, manual certificate intervention since MS's automatic cert update method cannot work. How to do that is linked late in the thread. https://www.bleepingcomputer.c...od-caused-by-scheduled-task Secure Boot wasn't at all important for this particular PC, so I disabled it to be done with the problem.
    • Winhance 26.06.12 by Razvan Serea Winhance is an open-source Windows enhancement utility designed to help users debloat, optimize, and customize Windows 10 and 11. It provides a user-friendly interface for removing unwanted apps, legacy components, and optional features safely, giving you more control over your system. With Winhance, you can improve performance, reduce clutter, and enhance privacy without the need for a clean install. Beyond basic debloating, Winhance offers extensive optimization tools. Users can tweak power plans, adjust gaming and performance settings, control notifications, and manage Windows Update behavior. Privacy-focused settings allow you to limit telemetry and data collection, while system customization options let you personalize the taskbar, Start menu, Explorer, and Windows themes. Winhance also supports installing or removing software efficiently, including external apps via WinGet integration, streamlining both new setups and daily maintenance. New AI privacy groups have been added for Windows AI, Microsoft Edge AI, and Microsoft Office AI, giving users clearer control over AI-related telemetry and feature usage. In addition, new settings in Gaming & Performance introduce AI taskbar pin toggles, options to remove AI apps, and controls for AI services and scheduled tasks, allowing users to better manage how AI components run in the background and appear in the system. For advanced users and IT professionals, Winhance integrates WIMUtil, a tool for creating custom Windows installation ISOs with automated configuration. You can generate autounattend.xml files, inject drivers, and apply your chosen Winhance settings automatically during installation. Most changes are non-destructive and reversible, with clear explanations in the GUI. Whether you’re optimizing a single PC or managing multiple systems, Winhance delivers a faster, cleaner, and highly personalized Windows experience. The Winhance.Installer.exe includes both Installable and Portable versions during setup. Winhance supports both Windows 10 and Windows 11 64-bit versions. It's regularly updated to ensure compatibility with the latest Windows updates and features. Winhance key features: Debloat Windows – Safely remove unwanted apps, features, and legacy components. Optimize Performance – Tune system settings for speed, responsiveness, and gaming. Privacy Enhancements – Control telemetry, data collection, and notifications. Power Management – Configure power plans and advanced energy settings. Windows Update Control – Adjust update behavior for stability and convenience. Theme Customization – Switch between light/dark mode and adjust system colors. Taskbar & Start Menu Tweaks – Modify layout, icons, and behavior. Explorer Customization – Adjust file explorer appearance and functionality. Software Management – Install/remove Windows apps and optional features. External Apps Installation – Deploy essential apps via WinGet integration. Configuration Management – Save, export, and import Winhance settings easily. Automation with WIMUtil – Create custom Windows ISOs with integrated settings. Autounattend.xml Generator – Automate Windows installations with preconfigured options. Driver Integration – Include current system drivers in custom ISOs. Non-Destructive Changes – Reversible settings with clear explanations in the GUI. Winhance 26.06.12 changelog: Features Builder Mode — build a Winhance config file or autounattend.xml without changing anything on the PC you're sitting at. Flip the new mode switcher to Builder, set everything the way you want it, and save the result as a Winhance config or an autounattend file ready for deployment on other machines. Sponsors & Supporters page — the exit donation dialog is gone. In its place, an in-app page (heart icon or the More menu) recognizes the businesses and individual supporters who keep Winhance free. It works offline and is fully localized. Change History — Winhance now keeps a receipt of everything it does. ChangeHistory.txt records every setting change (before and after values) and every app install or removal, with clear headers for config imports and bulk actions. Open it from the More menu. Hebrew language support — Winhance is now available in 29 languages. New Explorer customizations: desktop icon visibility toggles, This PC folder visibility, an icon cache size setting, and automatic thumbnail cache cleanup. New "All apps view" setting for the redesigned Windows 11 Start menu, and the Windows 11 system tray icons setting is now a dropdown with more control. App-local UI zoom — press Ctrl +/-/0 or use Ctrl+MouseWheel to scale the whole app, just like a browser. New External Apps: EA app, Ubisoft Connect, Battle.net, Rockstar Games Launcher, PowerShell, and Helium Browser. Bug Fixes Layouts no longer clip when the Windows text size slider is set above 100%. Accessibility: Narrator now announces setting names on toggles and dropdowns, previously unlabeled buttons are labeled, and progress updates are announced. Silent updates now respect your custom install location instead of reverting to the default. Cancel in Review Mode no longer clears your app selections. OneNote is now detected correctly for Win32 Click-to-Run installs. Clean Start Menu applies more reliably by also writing the group policy path. WinGet errors are no longer silent — error details now show in the terminal output. Fixed a startup crash on older Windows builds caused by a .NET runtime regression. Config import now converts power setting values correctly and no longer re-applies an already-active power plan. Improvements App icons load noticeably faster and cover almost everything now, including legacy capabilities and optional features — they come from a dedicated, checksum-validated icon repository and are fetched in parallel. Software & Apps polish: per-icon tooltips, extra table columns, an app sort dropdown, relocated search, and a cleaner compact view. A warning now appears when the Connected Devices Platform Service is set to Manual or Disabled, since some Windows features depend on it. Download: Winhance 26.06.12 | 61.5 MB (Open Source) Links: Winhance Website | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • 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
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      95
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!