-----BEGIN PGP SIGNED MESSAGE-----
We've opened the box for the Fedora 19 "Schrödinger's Cat" beta release
and confirmed it's alive! Ready to purr at the latest free and open
source technology? Download it now:
**** What is the Beta release? ****
The Beta release is the last important milestone before the release of
Fedora 19. Only critical bug fixes will be pushed as updates, leading
up to the general release of Fedora 19. Join us in making Fedora 19 a
solid release by downloading, testing, and providing your valuable
Of course, this is a beta release, meaning that some problems may still
be lurking. A list of the problems we already know about is found at
the Common F19 bugs page, seen here:
Fedora 19 Beta's default configuration allows applications and users
with administrative privileges to install signed packages from the
official Fedora repositories (but no other packages) without
authentication or confirmation. This was inherited from PackageKit
upstream, is not Fedora's intended behavior, and will not be the case
for the Fedora 19 final release. More details on this issue and the
planned behavior for the final release can be found at
**** Features ****
Fedora 19 continues our long tradition of bringing the latest
technologies to open source software users. No matter what you do with
open source, Fedora 19 has the tools you need to help you get things
A complete list with details of each new feature is available here:
=== Make new things ===
Would you like to play? Whether you're a developer, maker, or just
starting to learn about open source development, we have what you need
to bring your ideas to reality. Here's a peek at some of our new tools:
* 3D modelling and printing are enabled through a variety of tools,
including OpenSCAD, Skeinforge, SFACT, Printrun, and RepetierHost. By
bringing 3D printing tools into Fedora, you can get started with
what's ready-to-go in the repositories without having to download
binary blobs or run Python code from git.
* OpenShift Origin makes it easy for you to build your own
Platform-as-a-Service (PaaS) infrastructure, allowing you to enable
others to easily develop and deploy software.
scalable network applications or real-time apps across distributed
devices. Also included is the npm package manager, providing access
to over 20,000 programs and libraries available under free and open
* Ruby 2.0.0, just released in February, comes to Fedora while
maintaining source-level backwards compatibility with your Ruby 1.9.3
software. Also included: a custom Ruby loader for easy switching of
* MariaDB, a community-developed fork of MySQL, is the default
implementation of MySQL in Fedora 19, offering users a truly open
=== Get things done ===
* Federated VOIP means Fedora users can make calls using a user@domain
address with the same convenience as email.
* CUPS has been updated to the latest upstream release, using PDF
rather than PostScript as the baseline document format.
=== Learn ===
* Developer's Assistant is great for those new to development or even
new to Linux, this tool helps you to get started on a code project
with templates, samples, and toolchains for the languages of your
choice. Bonus: It lets you publish directly to GitHub.
=== Deploy, Monitor, and Manage ===
Make your machines work for you--not the other way around. Whether you
have one or "one too many" machines, Fedora 19 helps you boot manage
your systems and enables you to be proactive with tools for diagnosis,
monitoring, and logging.
* Syslinux optional boot tool integration brings you optional,
simplified booting of Fedora. We have added support for using
syslinux instead of GRUB via kickstart and plan to add a hidden
option in Anaconda installer as well. syslinux is especially ideal
for images used in cloud environments and virt appliances where the
advanced features of GRUB are not needed.
* Among other systemd enhancements in this release, systemd Resource
Control lets you modify your service settings without a reboot by
dynamically querying and modifying resource control parameters at
* Kerberos administrators will enjoy an easier experience, thanks to
Fedora 19 removing the need for Kerberos clients to sync their clocks
or to have reverse DNS records carefully setup for services. In
addition, it provies Kerberos-enabled, LDAP replicated, two-factor
authentication for FreeIPA.
* OpenLMI is a common infrastructure for the management of Linux
systems that makes remote management of machines much simpler.
**** Desktop Environments and Spins ****
=== GNOME 3.8 ===
GNOME 3.8 brings new applications such as clock and improvements to the
desktop including privacy and sharing settings, ordered search,
frequent applications overview, and additionally provides the ability
to enable a "classic mode" for a user experience similar to GNOME 2
built out of a collection of GNOME Shell extensions. Refer to
https://help.gnome.org/misc/release-notes/3.8/ for more details.
=== KDE Plasma Workspaces 4.10 ===
A modern, stable desktop environment, KDE Plasma Workspaces 4.10
includes new features for printing and screenlocking, better indexing
of files, and improved accessibility features. Refer to
http://www.kde.org/announcements/4.10/ for more details.
=== 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. You can read more about Fedora's Spins here:
Interest-specific Spins include the Design Suite Spin, the Robotics
Spin, and the Security Spin, among others. Other available desktop
environments, in addition to the GNOME 3.8 desktop which is shipped in
the default version of Fedora 19, as well as those highlighted above,
include Xfce, Sugar on a Stick, and LXDE.
To see all of the Official Fedora 19 Release Spins, see the Fedora 19
Release Spins link: https://fedoraproject.org/wiki/Releases/19/Spins
Nightly composes of alternate Spins are available here:
**** Contributing ****
We can't build Fedora inside a box. We need your help! Bug reports are
especially helpful--if you encounter any issues, please report them!
Fedora is a fantastic, friendly community, and we have many ways in
which you can contribute, including documentation, marketing, design,
QA, and development.
To learn how to help us, visit:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
-----END PGP SIGNATURE-----
there was a release of libical 1.0 recently , and I'd like to update
rawhide with it. It seems to be API compatible with 0.48, they only
bumped the soname version due to version jump to 1.0. Rex Dieter helped
me to fix a spec file to it (to use cmake), thus I plan to push the
change around May 23rd, 2013, aka at the end of the next week.
I tried to build evolution packages locally against it and there was no
build issue, thus it might be just about rebuilding other dependent
packages  and check whether any workarounds for 0.48 are still needed
(I see some changes in iCalendar file saving, most notably with
timezones (nothing serious with respect of functionality, saved files
are only significantly larger due to saving whole history of daylight
saving time changes) and string escaping, with which were couple issues
in 0.48). Maybe there will be more packages due to transitive dependency
(like other evolution packages is missing in ).
I'll take care of the rebuild of packages I've commit rights for,
the rest will be left for respective maintainers.
 Packages from rawhide found by
$ repoquery --archlist=src --repoid=fedora-source
--repoid=updates-source --repoid=updates-testing-source -q
--whatrequires --alldeps --releasever=rawhide libical-devel | sort
(*) these 3 I have commit rights for
At the Fedora 19 Beta Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 19 Beta by Fedora QA, FPL, FPGM and
Fedora 19 Beta will be publicly available on Tuesday, May 28, 2013.
Many thanks to everyone who helped with this release, as Viking-Ice
said, dont let Schrödinger's Cat escape the Beta bag!
Meeting details can be seen here:
Reminder: the Readiness meeting follows Go/No-Go meeting at
19:00 UTC, please join us to make sure we are well coordinated
for the release!
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 19 Beta.
Thursday, May 23, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"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."
For more details about this meeting see:
In the meantime, keep an eye on the Fedora 19 Beta Blocker list:
Reminder: the Readiness meeting follows the Go/No-Go meeting two
It is time again to begin Fedora's election season. This announcement contains information regarding the Fedora 20 Naming Election, as well as the Fedora Board, Fedora Engineering Steering Committee (FESCo), and Fedora Ambassadors Steering Committee (FAmSCo) elections.
** Fedora 20 Naming Election **
The suggestion period for names for Fedora 20 is now open (May 15, 2013), and will end promptly at the end of the day on May 22, 2013 (23:59:59 UTC). So run - don't "paws" - and get your suggestion in for the next Fedora release name.
You *must* follow the instructions and guidelines at the page listed above if you want your name to be considered. For instance, there must be an "is-a" link between the name "Schrödinger's Cat" (from Fedora 19) and the name you suggest. That link must be different than previous links for Fedora release names. Names of living people and well-known trademarks will likely be rejected as well.
You can also find full schedule details for the release naming process on the above page. For those of you interested in reviewing the history of Fedora release names, there exists an appropriately named wiki page for doing so: http://fedoraproject.org/wiki/History_of_Fedora_release_names
** Fedora Board, FESCo, and FAmSCo Elections **
The nomination period for elections for the Fedora Board, FAmSCo (Fedora Ambassador Steering Committee), and FESCo (Fedora Engineering Steering Committee) is now open, and will conclude at the end of day, May 25, 2013 (23:59:59 UTC).
This election cycle will fill the following seats for a one-year period:
* Fedora Board: 3 elected seats (2 additional seats will be appointed according to schedule)
* FESCo (Fedora Engineering Steering Committee): 5 elected seats
* FAmSCo (Fedora Ambassadors Steering Committee): 4 elected seats
Full information about the committee elections, including the elections schedule, and links to where one may nominate, can be seen here:
Additionally, the elections questionnaire is NOW OPEN for adding questions which will be posed to candidates for the listed groups. Following the closing of the questionnaire, candidates will be asked to answer questions relevant to the position for which they are seeking election. Questions may be added until May 23, 2013 (you guessed it - 23:59:59 UTC). Questions should be added here: https://fedoraproject.org/wiki/Elections/Questionnaire
Further information regarding each body's election follows below. As always, I encourage everyone to consider serving in an elected seat, or to encourage others that they feel would represent Fedora well to run for election.
Finally: I'd like to send a special thank-you to Ankur Sinha for once again helping to coordinate elections and the elections schedule. Your work here is greatly appreciated!
== Fedora Board ==
This election cycle will fill three elected seats for the Board (seats E3, E4, and E5). Two appointed seats (A3 and A4) will also be filled this cycle.
== FESCo ==
This cycle will see candidates elected to five open seats in the Fedora Engineering Steering Committee. For information on the nominations and elections, see:
== FAmSCo ==
This election cycle will see candidates elected to fill four open seats on the Fedora Ambassadors Steering Committee. For more information, refer to:
The Fedora Packaging Committee has one open seat and is accepting
submissions from interested candidates to serve on the FPC.
The FPC would like to thank Rex Dieter for his service, as he is
stepping down after several years.
This position involves not only reviewing Packaging Guideline drafts
submitted to the FPC for consideration, but also rewriting drafts
(sometimes from scratch) to resolve the issue in a more acceptable
fashion. Additionally, the FPC reviews bundling exceptions (and UID/GID
soft static assignment). The FPC meets on IRC weekly, Wednesdays at 1600
UTC, for approximately an hour. FPC members serve for as long as they
are willing, there are currently no term limits. All decisions are voted
on using a +1 (for), 0 (abstain), and -1 (against) mechanism, and all
decisions must be approved by a majority (+5). FPC Meetings do not
happen if quorum (5) is not present.
Candidates who are interested should provide the following details to
the FPC for consideration, by emailing it directly to me
(tcallawa(a)redhat.com). The FPC will consider all candidates, but
strongly prefers candidates who have extensive experience packaging in
Fedora. We will accept applications for the next week (deadline
Wednesday Apr 24, 2013).
Main area of packaging interest/expertise:
Reason(s) for wanting to join the FPC:
Thanks in advance,
This is a friendly reminder - all Features has to be 100% complete in
one week - by Tue May 14 2013, see the current schedule .
Please make sure to update your Feature(s) page(s) on time. In case of
any problems, let me know, we will try to find a solution. You can
find automatically generated report on Fedora Wiki .
FYI the Beta Change Deadline is early the same day and Beta freeze
will be in effect - only accepted blocker bugs and freeze exceptions
will be pulled into Beta!
Your friendly Feature Wrangler