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.
Recall that the infrastructure team has been working on a new notifications
system[1] in an attempt to unify some of the notifications that get pushed out
by our infrastructure. As the new system improves (and as we get time to clean
house), we will be turning off the native notifications of various systems.
- Back in February, the native emails from Koji were turned off[2].
- This past week, we turned off the old and well-loved emails from pkgdb[3] and
dist-git[4].
For your personal notifications, the default settings in FMN[5] should get you
what you need.
There are some mailing lists that had been archiving direct notifications from
from pkgdb and dist-git and we've been working to add those into the new
system. The scm-commits[6] and perl-devel[7] lists are working as expected
now. The meetingminutes list[8] now also automatically receives meeting minutes
from FMN, so, no need to go and send your minutes there if you have chaired an
irc meeting.
If you own a mailing list that has mysteriously stopped receiving automated
emails, please file an issue[9] requesting that we set up forwarding for you.
** P.S., unrelated, but zodbot grew a new feature recently: the "#help"
command is available in IRC meetings to let you solicit help from the
broader community on.. anything. Use it liberally. We'll be building a
"calls for help" web UI around it in the coming year.
[1] - https://lists.fedoraproject.org/pipermail/devel-announce/2014-September/001…
[2] - https://lists.fedoraproject.org/pipermail/devel-announce/2015-February/0015…
[3] - https://admin.fedoraproject.org/pkgdb
[4] - http://pkgs.fedoraproject.org/cgit/
[5] - https://apps.fedoraproject.org/notifications
[6] - https://lists.fedoraproject.org/pipermail/scm-commits/
[7] - https://lists.fedoraproject.org/pipermail/perl-devel/
[8] - https://lists.fedoraproject.org/pipermail/meetingminutes/
[9] - https://github.com/fedora-infra/fmn/issues/new
Hi!
This is a reminder, that Fedora 22 Change Checkpoint: 100% Code
Complete Deadline is coming in two weeks. It's important milestone
as for this release, we'd like to strictly adhere to schedule and
contingency plan may be put into effect for Changes that miss
this deadline. As always, the list will be shared with FESCo.
2015-03-31 Change Checkpoint: 100% Code Complete Deadline
2015-03-31 Fedora 22 Beta Freeze
Expected bug state is ON_QA - Change has to be code complete and
can be tested in the Beta release (optionally by Fedora QA).
Please make sure to update state of yours Change(s) bug(s) on time.
In case of any problems, let me know, we will try to find working
solution.
http://fedoraproject.org/wiki/Releases/22/Schedule
Expect more nagging in Change bug(s) between now and Beta Freeze ;-).
Thanks
Jaroslav
= Proposed Self Contained Change: Disabled Repositories Support =
https://fedoraproject.org/wiki/Changes/DisabledRepoSupport
Change owner(s): Richard Hughes <rhughes at redhat dot com>
The Software tool and PackageKit now support disabled repositories to help
users locate software in additional repositories which are not meant to be
enabled by default.
* This Change is announced after the Change Submission Deadline as an
exception to the process. May not be approved for proposed Fedora release. *
== Detailed Description ==
This feature aims to reduce the technical hurdles for users and developers to
locate software packaged for a distribution, but which needs to be clearly
identified as not officially included (or possibly sanctioned) by that
distribution.
When Software (via PackageKit) queries a repo definition that contains the line
enabled_metadata=1, even if the repo is disabled, it will download repodata.
This feature allows a user to locate software in response to a search. If the
user wants to install the software, she receives a dialog with information
that the repo must be enabled to satisfy the request, and if relevant,
information about the nature of the software (for instance, if it is non-
libre).
N.B. This feature does not currently operate in Fedora, since no such repo
definitions are currently shipped. However, the feature could be used by
remixers, and in the future in Fedora in the event of a policy change.
== Scope ==
* Proposal owners: Include enhancements in gnome-software/PackageKit (done)
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
** Note: For this feature to be used in Fedora requires an additional *-
release-extra package to ship disabled repo definition
* Policies and guidelines: N/A (not a System Wide Change)
** Note: For this feature to be used in Fedora requires clearer approval from
FESCo and the Council
Hello,
If your package is one of the packages affected with the hardening
change (F23/rawhide), please block:
[Bug 1199775] Tracking bug for issues with using the Hardened Flags
(Fails to Build, segfaults etc.) -
https://bugzilla.redhat.com/show_bug.cgi?id=1199775
If you decide to add '%undefine _hardened_build' to your spec file
would appreciate a comment above this line pointing to your bug (which
blocks the above tracking bug).
Thanks.
- Moez Roy
-----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-----
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
and Development.
Fedora 22 Alpha will be publicly available on Tuesday, March 10, 2015.
Meeting details can be seen here:
Minutes: http://bit.ly/17Y8Je5
Log: http://bit.ly/1Em9JXo
Thanks everyone! It's pretty solid Alpha release and on time :).
Jaroslav
Hi!
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 [1].
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
#fedora-meeting-2 channel.
[1] http://bit.ly/1H0LMmC
= Proposed Self Contained Change: Xfce412 =
https://fedoraproject.org/wiki/Changes/Xfce412
Change owner(s): Kevin Fenzi <kevin(a)scrye.com>, Mukundan Ragavan
<nonamedotc(a)fedoraproject.org>, Christoph Wickert <cwickert(a)fedoraproject.org>
Update Xfce to the new 4.12 release with a number of bugfixes and improvements.
* This Change is announced after the Change Submission Deadline as an
exception to the process. May not be approved for proposed Fedora release. *
== Detailed Description ==
Upstream Release Date: 2015-02-28
This release will have a number of bugfixes and improvements, but no radical
changes.
== Scope ==
* Proposal owners: Update Xfce packages. Update Xfce spin with any needed
adjustments.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)