The Fedora 20 "Heisenbug" alpha release has arrived with a preview of the latest fantastic, free, and open source technology currently under development. Take a peek inside:
What is the Alpha Release?
The Alpha release contains all the exciting features of Fedora 20 in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 20 is due expected in late November.
We need your help to make Fedora 20 the best release yet, so please take some time to download and try out the Alpha and make sure the things that are important to you are working. If you find a bug, please report it – every bug you uncover is a chance to improve the experience for millions of Fedora users worldwide. Together, we can make Fedora a rock-solid distribution. We have a culture of coordinating new features and pushing fixes upstream as much as feasible and your feedback will help improve not only Fedora but Linux and free software on the whole. (See the end of this announcement for more information on how to help.)
10 Years of Fedora
The Fedora 20 release coincides nicely with the 10th anniversary of Fedora. The first Fedora release (then called Fedora Core 1) came out on November 6, 2003.
Since then, the Fedora Project has become an active and vibrant community that produces nearly a dozen "spins" that are tailor made for desktop users, hardware design, gaming, musicians, artists, and early classroom environments.
ARM as a Primary Architecture
While Fedora has supported a number of hardware architectures over the years, x86/x86_64 has been the default for the majority of Fedora users and for the Linux community in general.
ARM, however, has been making massive strides. It already dominates the mobile market, and is becoming a go-to platform for hobbyists and makers, and is showing enormous promise for the server market as well.
In keeping with Fedora's commitment to innovation, the Fedora community has been pushing to make ARM a primary architecture to satisfy the needs of users and developers targeting the ARM platform.
Maturity and Advanced Features
Sometimes it's not the big new features that make a users' experience better, it's the little enhancements or long-awaited tricky features that really help make a new release the bee's knees.
NetworkManager is getting several improvements in Fedora 20 that will be welcome additions for power users and system administrators.
Users will now be able to add, edit, delete, activate, and de-activate network connections via the nmcli command line tool, which will make life much easier for non-desktop uses of Fedora.
NetworkManager is also getting support for bonding interfaces and bridging interfaces. Bonding and bridging are used in many enterprise setups and are necessary for virtualization and fail-over scenarios.
No Default Sendmail, Syslog
Fedora 20 removes some services that many users find unnecessary, though (of course) they will remain available as installable packages for users who might need them.
The systemd journal now takes the place as the default logging solution, having been tested and able to manage persistent logging in place of syslog.
Also, Sendmail will no longer be installed by default, as most Fedora installs have no need of a Mail Transfer Agent (MTA).
Cloud and Virtualization Improvements
The Fedora 20 release continues the Fedora tradition of adopting and integrating leading edge technologies used in cloud computing. This release includes a number of features that will make working with virtualization and cloud computing much easier.
OS Installer Support for LVM Thin Provisioning
LVM has introduced thin provisioning technology, which provides greatly improved snapshot functionality in addition to thin provisioning capability. This change will make it possible to configure thin provisioning during OS installation.
VM Snapshot UI with virt-manager
This feature will make taking VM snapshots much easier. qemu and libvirt have all the major pieces in place for performing safe VM snapshots/checkpoints, however there isn't any simple discoverable UI. This feature will track adding that UI to virt-manager, and any other virt stack bits that need to be fixed/improved. This includes adding functionality to libvirt to support deleting and rebasing to external snapshots.
Vagrant is an automation tool used to manage development environments using virtualization and configuration management tools. It allows developers and teams to work on their projects and test them in an environment similar to production. Historically, Vagrant had a dependency on VirtualBox, but the Vagrant Support|newer versions have a plugin system allowing it to work with other virtualization technologies, including KVM.
Role based access control with libvirt
Libvirt role based access control will allow fine grained access control like 'user FOO can only start/stop/pause vm BAR', but for all libvirt APIs and objects.
ARM on x86 with libvirt/virt-manager
Fix running ARM VMs on x86 hosts using standard libvirt tools libvirt virsh, virt-manager and virt-install.
Fedora prides itself on bringing cutting-edge technologies to users of open source software around the world, and this release continues that tradition. No matter what you do, Fedora 20 has the tools you need to help you get things done.
A complete list with details of each new feature is available here:
Desktop Environments and Spins
Spins are alternate versions of Fedora. In addition to various desktop environments for Fedora, spins are also available as tailored environments for various types of users via hand-picked application sets or customizations.
To see all of the Official Fedora 20 Release Spins, see the Fedora 20 Release Spins link.
Nightly composes of alternate Spins are available here: http://dl.fedoraproject.org/pub/alt/nightly-composes
Note on performance
Fedora development releases use a kernel with extra debug information to help us understand and resolve issues faster; however, this can have a significant impact on performance. Refer to kernel debug strategy for more details. You can boot with slub_debug=- or use the kernel from nodebug repository to disable the extra debug info.
Issues and Details
Heisenbug Alpha is a testing release. To report issues encountered during testing, contact the Fedora QA team via the test mailing list or in #fedora-qa on freenode.
As testing progresses, common issues are tracked at https://fedoraproject.org/wiki/Common_F19_bugs
For tips on reporting a bug effectively, read http://fedoraproject.org/wiki/How_to_file_a_bug_report .
There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, design and do artwork, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today!
<jreznik> #link https://bugzilla.redhat.com/buglist.cgi?component=Changes%20Tracking&list_id=1691171&product=Fedora * jnalley (~jnalley@fedora/jnalley) has left #fedora-meeting <jreznik> MODIFIED changes should be testable and mostly done <jreznik> suehle: ARM as primary is pretty interesting one <jreznik> but we do not promise it to stay primary architecture for final release <jzb> Perl 5.18, woohoo! <jzb> NWM bonding support is actually pretty cool <jreznik> what needs coverage is no default sendmail and rsyslog <jreznik> it's still ASSIGNED but should be done (just not updated) <jreznik> jzb: also NM CLI is pretty nice feature <jzb> jreznik: application installer shows MODIFIED but if I'm reading the items correctly probably too early to mention? <jreznik> jzb: there is initial implementation <jreznik> already in F20 and will in alpha