-----BEGIN PGP SIGNED MESSAGE-----
Fedora 22 Alpha Release Announcement
The Fedora 22 Alpha release has arrived, with a preview of the latest
free and open source technology under development. Take a peek inside!
• Get Fedora 22 Alpha Workstation
• Get Fedora 22 Alpha Server
• Get Fedora 22 Alpha Cloud
• Get Fedora 22 Alpha Spins
What is the Alpha release?
The Alpha release contains all the exciting features of Fedora 22's
editions 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 22 is expected in May.
We need your help to make Fedora 22 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 well. 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 22 another rock-solid release. 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.
Fedora 22 Cloud
The Fedora 22 Cloud Edition builds on the work completed during the
Fedora 21 cycle, and brings in a number of improvements that make
Fedora 22 a superb choice for running Linux in the cloud.
Ready for the Fedora 22 release, we have:
• The latest versions of rpm-ostree and rpm-ostree-toolbox. You can
even use rpm-ostree-toolbox to generate your own Atomic hosts from
a custom set of packages.
• A Vagrant image for Fedora 22 Atomic Host and Cloud Images. We're
supplying Vagrant boxes that work with KVM or VirtualBox, so users
on Fedora will be able to easily consume the Vagrant images with
KVM, and users on Mac OS X or Windows can use the VirtualBox image.
• Tunir: A new, lightweight Continuous Integration (CI) tool for
rapid testing of cloud images. While being driven by the need for
simple CI for the Cloud Working Group, it's generic enough to be
used by anyone to configure and run jobs/tests on their local
Fedora 22 Server
The Fedora 22 Server Edition brings several changes that will improve
Fedora for use as a server in your environment.
• Database Server Role: Fedora 21 introduced Rolekit, a daemon for
Linux systems that provides a stable D-Bus interface to manage
deployment of server roles. The Fedora 22 release adds onto that
work with a database server role based on PostgreSQL.
• Cockpit Updates: The Cockpit Web-based management application has
been updated to the latest upstream release which adds many new
features as well as a modular design for adding new functionality.
Fedora 22 Workstation
As always, Fedora carries a number of improvements to make life better
for its desktop users! Here's some of the goodness you'll get in Fedora
22 Workstation edition.
• The GNOME Shell notification system has been redesigned and
subsumed into the calendar widget.
• The Terminal now notifies you when a long running job completes.
• The login screen now uses Wayland by default. This is a step
towards replacing X with Wayland, and users should not actually
notice the difference.
• Installation of GStreamer codecs, fonts, and certain document types
is now handled by Software, instead of gnome-packagekit.
• The Automatic Bug Reporting Tool (ABRT) now features better
notifications, and uses the privacy control panel in GNOME to
control information sent.
• The Nautilus file manager has been improved to use GActions, from
the deprecated GtkAction APIs, for a better, more consistent
• The GNOME Shell has a refreshed theme for better usability.
• The Qt/Adwaita theme is now code complete, and Qt notifications
have been improved for smoother experience using Qt-based apps in
Under the covers:
• The libinput library is now used for both X11 and Wayland for
consistent input device handling.
• Plasma 5, the successor to KDE Plasma 4, is now the default
workspace in the Fedora KDE spin.
• The Xfce spin has been updated to Xfce 4.12 just in time for the
Alpha release. This release has an enormous number of improvements,
including HiDPI support, improvements to window tiling, support for
Gtk3 plugins, and many improvements for multi-monitor support.
Issues and Details
This is an Alpha release. As such, we expect that you may encounter
bugs or missing features. To report issues encountered during testing,
contact the Fedora QA team via the test mailing list or in #fedora-qa
As testing progresses, common issues are tracked on the Common F22 Bugs
For tips on reporting a bug effectively, read "how to file a bug
The full release schedule is available on the Fedora wiki:
The current schedule calls for a beta release in the middle of April,
and a final release in the second half of May.
These dates are subject to change, pending any major bugs or issues
found during the development process.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
# Fedora Quality Assurance Meeting
# Date: 2015-03-09
# Time: ** 15:00 UTC ** NOTE TIME CHANGE
# Location: #fedora-meeting on irc.freenode.net
It's QA meeting time again! Daylight savings kicks in in North America
(at least, my bit of it) this weekend, so I'm scheduling this meeting
for 15:00 UTC. If your clocks go back this weekend, the meeting should
be at the same local time as it was before. If your clocks don't go
back, it will be one hour earlier.
We signed off on Fedora 22 Alpha on Friday, so let's check we've done
all the rest of the necessary work around Alpha and do a bit of
planning ahead for Beta. We can also check in on upcoming Test Day
If you have any other topic ideas, please reply to this mail and we'll
add them in the meeting! Thanks folks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 22 Alpha final check-in
3. Fedora 22 Beta planning
4. Test Day check-in
5. Open floor
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
At the Fedora 22 Alpha Go/No-Go Meeting #2 that just occurred, it was
agreed to Go with the Fedora 22 Alpha by Fedora QA, Release Engineering
Fedora 22 Alpha will be publicly available on Tuesday, March 10, 2015.
Meeting details can be seen here:
Thanks everyone! It's pretty solid Alpha release and on time :).
Today at Fedora 22 Alpha Go/No-Go meeting it was decided that Fedora 22
Alpha is No-Go as no release candidate is available. More details in
meeting minutes .
But as we're looking pretty good and RC1 compose is undergoing right
now (estimate delivery is 3:00 UTC on Friday), we decided to try the
seconnd Go/No-Go meeting tomorrow. Earlier to give rel-eng chance to
prepare the content for mirroring.
The next Go/No-Go meeting is on Friday, Mar 06 8:30 AM CST/14:30 UTC
Hi, folks! Time (and past time) for a Fedora 22 blocker status review.
Sorry this is late; we've been fighting fires for the last week :(
Here are your outstanding blockers requiring attention from test,
devel, or both:
"network spoke listed as not connected despite having assigned IP and
hostname" - anaconda team have the impression that this is an ARM-
specific kernel issue to do with renaming of ethernet devices on ARM;
could do with input from ARM folks.
crash during kickstart" - this needs re-testing with the fixed
anaconda, except the 'fixed' anaconda is DOA due to other issues; I've
alerted the anaconda team to the issues.
cloud builds fail to boot with kernel panic" - this could do with a
status update; I get the impression it may be a bit out of date, but
as of now it shows as NEW. Could cloud folks please review?
FREEIPA / SSSD: https://bugzilla.redhat.com/show_bug.cgi?id=1197218
"Add missing dependencies into freeipa packages" - this still appears
to need attention, but it may no longer block release as
https://bugzilla.redhat.com/show_bug.cgi?id=1014594has been pulled in
as a freeze exception. It would be good to get clarification on the
current status - sgallagh?
FREEIPA: https://bugzilla.redhat.com/show_bug.cgi?id=1195811"PKI fails
to install, missing support for Tomcat 8.0" - the Tomcat 7 revert is
built and in updates-testing thanks to sgallagh, we will need to test
it now, whether with scratch images or by rolling a TC9 tomorrow.
"dhclient is started by NetworkManager at disconnection instead of at
connection time" - this seems to be a straight-up NM bug affecting
wired network connections on some hardware (at least recent Thinkpads)
that still requires developer attention.
XORG: https://bugzilla.redhat.com/show_bug.cgi?id=1196676"X fails to
start when booting x86_64 netinst on basic graphic mode (nomodeset)" -
this requires developer attention; it's been discussed on the list
already, but a fix hasn't appeared yet.
For testers, the list of builds requiring karma is quite light right
now. As anaconda is currently known to be broken, it's really only the
https://admin.fedoraproject.org/updates/tomcat-7.0.59-3.fc22. It would
help a lot if folks who are able to test FreeIPA deployments can test
with that Tomcat and confirm that FreeIPA works with it. We will
probably want to roll a new compose tomorrow, ideally with an updated
anaconda, but we cannot roll an RC yet due to several blockers still
being outstanding (most of the above).
As Go/No-Go is scheduled for Thursday we're unfortunately very likely
to slip Alpha at this point :( Despite our attempts to test earlier in
the cycle, many late-landing changes caused problems, and we were not
able to test the flavor/Product-ized images until the first TC landed.
The GCC rebuild certainly seems to have caused its fair share of havoc
:(. Aside from the bugs listed above we have a near-blocker for the
KDE images - https://bugzilla.redhat.com/show_bug.cgi?id=1194682-
which is still being worked on.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 22 Alpha.
Thursday, March 05, 2015 17:00 UTC (12 noon EST, 9 AM PST, 18:00 CET)
"Before each public release Development, QA and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is called the Go/No-Go Meeting."
"Verifying that the Release criteria are met is the responsibility of
the QA Team."
Release Candidate (RC) availability and good QA coverage are prerequisites
for the Go/No-Go meeting. We don't have RC yet as the list of accepted
blockers is still pretty long. If you have any bug on the list, please
help us with Alpha release. If we won't be ready by Thursday, we will
use this meeting to review blockers and decide what to do.
For more details about this meeting see:
In the meantime, keep an eye on the Fedora 22 Alpha Blocker list: