Advanced

Worth the wait: Fedora Linux 35 is here!

Posted by Scott_Ruecker on · 1 comment
Fedora Magazine; By Matthew Miller
Mail this story
Print this story

Today, I’m excited to share the results of the hard work of thousands of Fedora Project contributors: our latest release, Fedora Linux 35, is here! While we broke our six-release streak of on-schedule releases, we felt it was more important to resolve a few outstanding blocking bugs. Fedora believes that software has to be usable to be useful, so while we know that a predictable schedule is important, we also ensure that every release meets our criteria, no matter what the calendar says.

Full Story

  Nav
» Read more about: Story Type: News Story; Groups: Fedora, Linux

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (1)

I believe the procedure has been changed since Fedora 34

The issue I am experiencing in VENV is failure to restart libvirtd service after VM's restart regardless libvirtd service has been enabled previously.



Update as of 11/04/21

Attempt to upgrade F34 KVM Hypervisor to F35 KVM Hypervisor per suggested procedure causes Hypervisor's crash. It might be setup only on fresh F35 instance.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post