Language Selection

English French German Italian Portuguese Spanish

Ubuntu 20.10 Release Date & Planned Features (Continually Updated)

Filed under
Ubuntu

Now, admittedly, it’s only May; development of this release (which is codenamed ‘Groovy Gorilla’) is still in the early stages. But already know a few things about what to expect, when Ubuntu 20.10 will be released, how long it’ll be supported for, and even a few of the features devs are hoping to sneak in.

So keep reading to learn everything you need to know about Ubuntu 20.10 features, changes and improvements. And since this post is updated regularly throughout development why not bookmark it now to come check back and keep tabs on the progress!

Read more

Ubuntu 20.04.1 LTS (Focal Fossa) Slated for Release on July 23rd

  • Ubuntu 20.04.1 LTS (Focal Fossa) Slated for Release on July 23rd

    While many of you out there are still digging out all the cool new features of the recent Ubuntu 20.04 LTS (Focal Fossa) operating system or just barely took the wraps off it, the Ubuntu development team are working hard to bring you the next point release.

    Yes, I’m talking about Ubuntu 20.04.1 LTS, the first point release of the Focal Fossa series, which will pack all the latest security fixes and software updates to provide the community with an up-to-date installation media.

Ubuntu 20.04 is right around the corner with many new features

  • Ubuntu 20.04 is right around the corner with many new features

    Ubuntu 20.04 – codenamed “Focal Fossa” – is set for its final stable release on April 23, with the new software version brining a number of new features to the OS, including WireGuard VPN.

    Ubuntu 20.04 is a long term support (LTS) version of the operating system, meaning that it will be supported for the next 5 years to come. As usual, the new version introduces some features to the benefit of its users – with some features being more exciting than others. One of the more exciting new features is the inclusion of WireGuard – a simple, fast and modern VPN that has the backing of Linus Torvalds, the creator of Linux.

Ubuntu 20.04.1 LTS Coming on July with Fixes Packed

  • Ubuntu 20.04.1 LTS Coming on July with Fixes Packed

    The first point release of the Ubuntu 20.04 LTS is planned for release on July 2020. Ubuntu 20.04 LTS “Focal Fossa” released a while back and it was huge. The reason being are the performance improvements, stability, lots of features, latest drivers, and hardware support – all on the very positive side from the user perspective. At least, that’s what the post-release feedback from around the world says.

    [...]

    Ubuntu 20.04 LTS is supported until April 2025 bing a long term release and expected to get six point releases like this in its life span.

    If you are currently running Ubuntu 20.04 LTS focal fossa – you will be prompted to update/upgrade when Ubuntu 20.04.1 arrives in July. And if you are still deciding to update or upgrade, I would suggest you can wait till July 2020 to get the latest packages afresh.

First Ubuntu 20.04 Point Release Arrives July 23

  • First Ubuntu 20.04 Point Release Arrives July 23

    But the upcoming release is not totally lacking in interest.

    From July 23 users of Ubuntu 18.04 LTS will finally be notified that ‘a newer version of Ubuntu is available’ and, if they wish to upgrade to Ubuntu 20.04 LTS, be able to do so.

    Ubuntu LTS releases only check for new LTS releases by default, and even then only “see” a new release once the first point release is made available.

    Why? Because LTS releases are about stability above all else. In a 5 year LTS cycle it’s not a huge issue to wait a couple of extra months. This way, users can be sure any early-bird bugs have been spotted, swooped on, and chowed down!

Comment viewing options

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

More in Tux Machines

Kernel: Virtualisation, BPF, and Btrfs

  • QEMU 5.1 Bringing Many CPU Improvements From Loongson To RISC-V To s390

    QEMU 5.1-rc0 is available as the first step towards this next feature release of this important component to the Linux virtualization stack. The QEMU 5.1-rc0 release marks the hard feature freeze for this next release. Weekly release candidates will continue until QEMU 5.1 is ready to ship around the middle of August.

  • Sleepable BPF programs

    When support for classic BPF was added to the kernel many years ago, there was no question of whether BPF programs could block in their execution. Their functionality was limited to examining a packet's contents and deciding whether the packet should be forwarded or not; there was nothing such a program could do to block. Since then, BPF has changed a lot, but the assumption that BPF programs cannot sleep has been built deeply into the BPF machinery. More recently, classic BPF has been pushed aside by the extended BPF dialect; the wider applicability of extended BPF is now forcing a rethink of some basic assumptions. BPF programs can now do many things that were not possible for classic BPF programs, including calling helper functions in the kernel, accessing data structures ("maps") shared with the kernel or user space, and synchronizing with spinlocks. The core assumption that BPF programs are atomic has not changed, though. Once the kernel jumps into a BPF program, that program must complete without doing anything that might put the thread it is running in to sleep. BPF programs themselves have no way of invoking any sort of blocking action, and the helper functions exported to BPF programs by the kernel are required to be atomic. As BPF gains functionality and grows toward some sort of sentient singularity moment, though, the inability to block is increasingly getting in the way. There has, thus, been interest in making BPF programs sleepable for some time now, and that interest has recently expressed itself as code in the form of this patch set from Alexei Starovoitov. The patch adds a new flag, BPF_F_SLEEPABLE, that can be used when loading BPF programs into the kernel; it marks programs that may sleep during their execution. That, in turn, informs the BPF verifier about the nature of the program, and brings a number of new restrictions into effect. Most of these restrictions are the result of the simple fact that the BPF subsystem was never designed with sleepable programs in mind. Parts of that subsystem have been updated to handle sleeping programs correctly, but many other parts have not. That is likely to change over time but, until then, the functionality implemented by any part of the BPF subsystem that still expects atomicity is off-limits to sleepable programs. For example, of the many types of BPF programs supported by the kernel, only two are allowed to block: those run from the Linux security module subsystem and tracing programs (BPF_PROG_TYPE_LSM and BPF_PROG_TYPE_TRACING). Even then, tracing programs can only sleep if they are attached to security hooks or are attached to functions that have been set up for error injection. Other types of programs are likely to be added in the future, but the coverage will never be universal. Many types of BPF programs are invoked from within contexts that, themselves, do not allow sleeping — deep within the network packet-processing code or attached to atomic functions, for example — so making those programs sleepable is just not going to happen.

  • Btrfs at Facebook

    The Btrfs filesystem has had a long and sometimes turbulent history; LWN first wrote about it in 2007. It offers features not found in any other mainline Linux filesystem, but reliability and performance problems have prevented its widespread adoption. There is at least one company that is using Btrfs on a massive scale, though: Facebook. At the 2020 Open Source Summit North America virtual event, Btrfs developer Josef Bacik described why and how Facebook has invested deeply in Btrfs and where the remaining challenges are. Every Facebook service, Bacik began, runs within a container; among other things, that makes it easy to migrate services between machines (or even between data centers). Facebook has a huge number of machines, so it is impossible to manage them in any sort of unique way; the company wants all of these machines to be as consistent as possible. It should be possible to move any service to any machine at any time. The company will, on occasion, bring down entire data centers to test how well its disaster-recovery mechanisms work.

today's howtos

Home Assistant improves performance in 0.112 release

The Home Assistant project has released version 0.112 of the open-source home automation hub we have previously covered, which is the eighth release of the project this year. While previous releases have largely focused on new integrations and enhancements to the front-end interface, in this release the focus has shifted more toward improving the performance of the database. It is important to be aware that there are significant database changes and multiple potential backward compatibility breaks to understand before attempting an upgrade to take advantage of the improvements. According to the release notes written by contributor Franck Nijhof, better performance has been a major goal of this release with a focus on both the logbook and history components. This builds on the work of the previous release (v0.111) from a performance perspective, which focused on reducing the time it takes to initialize the hub at startup. Read more

Android Leftovers