Language Selection

English French German Italian Portuguese Spanish

'Ubuntu Needs a Longer Release Schedule!'

Filed under
Ubuntu




Here's what I suggest

Many of you have dabbled in what's known as rolling release distros - PCLinuxOS, Arch... My suggestion is that Ubuntu adopt a hybrid release system. In Novemeber, Ubuntu could release a completely new release with full version numbering. Follow that up with the Spring release that's a rolling release of the November release, only completely updated with the newest Gnome, KDE, kernel, etc.. This way, the Spring release would be rock solid stable, yet have all the newest stuff, but the Novemeber release would allow a complete rebase and reassembly to incorporate new technologies such as Grub2, Plymouth, etc..

RE:Here's what I suggest

That is what they are doing already with the .04 release roughly corresponding in intent to the Mandriva spring release and the .10 release getting new features by the kilo.

But the real point is that it remains to see whether a problem actually exists. I mean Karmic is the fastest, most stable Linux OS I ever used since 2002 and the very first one with full hardware support for my laptop.

I don't mean to be pro-Ubuntu or something, I don't care, tomorrow I might switch to another distro, but my take on the big Karmic problem is that Ubuntu is getting more eyes upon than Linux ever did, many many more. So instead of 10 blogs about it you now get 1000, and you get everything, including the garbage, written by people clueless or with a hidden agenda.

I'm not saying let's reject criticism, but certainly pay attention to what we read, the bar speech style of many of those "reviewers" speaks for itself.

I understand your point, but

I understand your point, but let me make it a point to say, no, it's not what they are currently doing. Currently, both the .04 and .10 releases are built from the ground up - a total rebuild. With a rolling release, the second release would be binary compatible with the first because it would be nothing more than the first release, updated with a new kernel and software updates to that point in time. More or less, simply rebuilding the ISO with updates included. This would allow a new kernel for newer hardware support, as well as the ability for Ubuntu to keep hammering out the bugs and giving the users a full year support for a release. Those that have installed the first release could just keep up to date in the repositories and not have to install the new ISO.

I see your point now

I missed your point before. What you say is something they can maybe do after Lucid, when they will have pretty much defined their OS in full, then they can afford to sit back and cut their development speed by half, which is what your scheme inevitably involves.

More or less, yes. It also

More or less, yes. It also provides a longer term of support for the release, yet keeps the software up to date. In reality, it sucks to reinstall or cross your fingers and do a dist-upgrade every 6 months. If that could be put off to be once a year, but updating through the repository would give newer kernels, Gnome, KDE, OpenOffice and such. Also, the second ISO would allow new users and users with newer hardware to get the latest hardware support and have fewer updates to get after installation. IMO, this is a win-win situation: Less development costs for Ubuntu, more stable releases, longer support for releases, less frequent full upgrades, newest hardware support, newest software releases, etc... Yet, once a year, it gets completely rebuilt to incorporate new technologies such as Grub2 and Plymouth more efficiently.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's howtos

Linux 4.15, Linux 4.16, and Linux Foundation's CNCF and CII

  • Linux 4.15 Gets Fixed To Report Current CPU Frequency Via /proc/cpuinfo
    A change recently in the Linux kernel led the CPU MHz reported value via /proc/cpuinfo to either be the nominal CPU frequency or the most recently requested frequency. This behavior changed compared to pre-4.13 kernels while now it's been fixed up to report the current CPU frequency.
  • Linux 4.16 Will Be Another Big Cycle For Intel's DRM Driver
    We are just through week one of two for the Linux 4.15 merge window followed by eight or so weeks after that before this next kernel is officially released. But Intel's open-source driver developers have already begun building up a growing stack of changes for Linux 4.16 when it comes to their DRM graphics driver.
  • CNCF Wants You to Use 'Certified Kubernetes'
  • Open Source Threat Modeling
    Application threat modeling is a structured approach to identifying ways that an adversary might try to attack an application and then designing mitigations to prevent, detect or reduce the impact of those attacks. The description of an application’s threat model is identified as one of the criteria for the Linux CII Best Practises Silver badge.

Linux World Domination and Microsoft Corruption in Munich

Programming/Development: 'DevOps', NumPy, Google SLING

  • 5 DevOps leadership priorities in 2018
    This week, DevOps professionals gathered in San Francisco to talk about the state of DevOps in the enterprise. At 1,400 attendees, the sold-out DevOps Enterprise Summit has doubled in size since 2014 – a testament to the growth of the DevOps movement itself. With an ear to this event and an eye on the explosion of tweets coming out of it, here are five key priorities we think IT leaders should be aware of as they take their DevOps efforts into the new year.
  • NumPy Plan for dropping Python 2.7 support
    The Python core team plans to stop supporting Python 2 in 2020. The NumPy project has supported both Python 2 and Python 3 in parallel since 2010, and has found that supporting Python 2 is an increasing burden on our limited resources; thus, we plan to eventually drop Python 2 support as well. Now that we're entering the final years of community-supported Python 2, the NumPy project wants to clarify our plans, with the goal of to helping our downstream ecosystem make plans and accomplish the transition with as little disruption as possible.
  • Google SLING: An Open Source Natural Language Parser
    Google Research has just released an open source project that might be of interest if you are into natural language processing. SLING is a combination of recurrent neural networks and frame based parsing. Natural language parsing is an important topic. You can get meaning from structure and parsing is how you get structure. It is important in processing both text and voice. If you have any hope that Siri, Cortana or Alexa are going to get any better then you need to have better natural language understanding - not just the slot and filler systems currently in use.