Fedora 22 Alpha Release Announcement
====================================
The Fedora 22 Alpha release for the AARCH64 and POWER 64 secondary architectures
has arrived, with a preview of the latest free and open source technology under
development. Take a peek inside!
• Get Fedora 22 Alpha Server
https://getfedora.org/en/server/prerelease/
• https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/22_Alpha/Se…
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 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.
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
on freenode.
As testing progresses, common issues are tracked on the Common F22 Bugs
page: https://fedoraproject.org/wiki/Common_F22_bugs
For tips on reporting a bug effectively, read "how to file a bug
report:" https://fedoraproject.org/wiki/How_to_file_a_bug_report
Release Schedule
================
The full release schedule is available on the Fedora wiki:
https://fedoraproject.org/wiki/Releases/22/Schedule
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.
<http://fedoramagazine.org/help-fedora-find-a-diversity-advisor/>
Increased diversity is crucial to the future of open source. A range of
contributors from varying backgrounds brings broader experience to the
table, which makes for healthier projects — and ultimately better
software. To make Fedora a more diverse community, the Fedora Council
(our new governance and leadership body) has an open position for a
Diversity Advisor, and we need your help to find the perfect person for
this role.
What does a Diversity Advisor do?
---------------------------------
The Fedora Diversity Advisor will lead initiatives to assess and
promote equality and inclusion within the Fedora contributor and user
communities, and will develop project strategy on diversity issues. The
Diversity Advisor will also be the point of contact for Fedora’s
participation in third-party outreach programs and events.
What’s happening now?
---------------------
We’re forming a search committee to find the most awesome and
incredible human being for the job — and this message is the invitation
to join that committee.
In earlier conversations, we’ve talked about the various benefits of
asking someone within the project to fill the role vs. inviting someone
from the outside, with experience in open source and communities but
not necessarily deeply with Fedora. There clearly are benefits and
disadvantages either way, and we’re open to either one. We’d like the
search committee to include both perspectives (as well as of course
different backgrounds and expertise with minority groups). That way, if
we choose someone external, we can feel confident that people with a
longer history within the project back the choice (and, indeed, were
part of making it); and if we choose someone from within Fedora, that
we also have the benefit of outside perspective in doing so.
How can I help?
---------------
If you’re interested in helping with the search, please email me at
<mattdm(a)fedoraproject.org> with answers to the following questions
(and/or anything else you’d like to say). I’ll share responses
confidentially with other members of the Fedora Council, and we’ll form
the committee from there.
1. Why do you believe diversity and inclusion are important for Fedora,
and why do you want to join the search team for Fedora’s Diversity
Advisor?
2. What specific minority group(s) or issues can you offer insight
about? What perspectives, experiences, or knowledge about diversity
and inclusion could you share as a member of the search team?
3. To give us further insight, feel free to provide names and contact
information for up to three people who can speak to your passion,
interest, or experience with diversity and inclusion.
Please send responses by March 31st, 2015, so we can get the search
underway. We will leave actual details of how the search will work up
to the searchers. It may end up that someone with interest in being on
the search team will also be the best candidate; the Council doesn’t
see that as a problem. And, it may be that the committee will want to
continue to exist after the search, in an advisory role or as part of
an action team, but we also don’t want to raise barriers by making that
an initial obligation.
Note that the Diversity Advisor currently an unpaid, volunteer
position. I personally hope we can change that in the future, but we
also wanted to take the steps we can *now* to make progress. This is
not a token role; it carries full participation in Council consensus
for any and all project issues relevant to diversity.
Please share!
-------------
Please share this invitation with anyone you think might be interested,
both within Fedora and outside of Fedora in relevant communities. Thank
you!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
https://getfedora.org/en/workstation/prerelease/
• Get Fedora 22 Alpha Server
https://getfedora.org/en/server/prerelease/
• Get Fedora 22 Alpha Cloud
https://getfedora.org/en/cloud/prerelease/
• Get Fedora 22 Alpha Spins
https://spins.fedoraproject.org/prerelease
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
system.
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.
Enhancements:
• 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.
Appearance:
• The Nautilus file manager has been improved to use GActions, from
the deprecated GtkAction APIs, for a better, more consistent
experience.
• 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
Workstation.
Under the covers:
• The libinput library is now used for both X11 and Wayland for
consistent input device handling.
Spins
• 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
on freenode.
As testing progresses, common issues are tracked on the Common F22 Bugs
page: https://fedoraproject.org/wiki/Common_F22_bugs
For tips on reporting a bug effectively, read "how to file a bug
report:" https://fedoraproject.org/wiki/How_to_file_a_bug_report
Release Schedule
================
The full release schedule is available on the Fedora wiki:
https://fedoraproject.org/wiki/Releases/22/Schedule
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
iQIcBAEBAgAGBQJU/vl4AAoJEH7ltONmPFDRK6sP/1dLHhetrjwNHFwQiZqwEH1A
wur8X0EVfzGLKlsf/MHACVV95LdeL6DozPaIs+a5PZZ+KVGvp3vBND24uqQEzKqz
la9hSKXccnb4ck80wRh3FN9lsEN/Dr1s7E18p5flEJYbgY4JLDJM+wj7tkReoKsF
I1eUhUvBeHREgNdf1dX5EUc3PzKbWvpf83NsZeS7zoH7rFCo6nW7zY4s1HkSeBbw
UZeEkdPCDfw1bpgJpeshE14MsezWSlR7NpiIKf9eGi5XGlD8B4KbLZvnks7A9eUX
Hm1ZBVMn2a4JlAZAD1H67xrV5V+F2oNgj6tty0fjUoKLEvGQObcVm8r4+57mTfXz
Onjou/65+9boiOMpCO78cHbPafCvaQYs7LoWpnteTCWxPaXSQFJWQUW624pL88nd
P+TpMFUG0h8Euuhig7VEz66taLz2EuhICERERMO+H3q+5Te3D05XcOFUdCbxNfkA
fcdvRIqYp7nOspnVdgiiP1jv4AeIZ/yBbqtyYOG/t9prz2vr1eOhvieZ+J0XNMpA
3RPihtRQD0hrpv/3BZ7/Xv2Uel7gg8ODA2MNL9I0tkmHW08I8qfFOUgMuRpeArSR
uPHvZod+CxmeZK6wUMqLLLj9pv/a/FXhT6T+7O+Mo6I23FqTbKVRIPQ7hVhUYpkk
pWLC0CMq1Yth9MW4QhKV
=NCvz
-----END PGP SIGNATURE-----