Build package with latest translation for l10n testing
by Ani Peter
Hello Fedora package maintainers,
Kindly build and push your packages with latest translation files (ie,
pull the latest translations from Transifex/Zanata) by FRIDAY
2013-09-27, for Fedora 20 L10n test scheduled on 2013-10-03 (Thursday).
The packages with latest translations can thus be used to create the
live image, which the language translators worldwide can use for testing
in their own languages on this test day. Any issues they find will be
filed as bug. Appreciate your help in this regard as this is an
opportunity for the translators to check and modify the translation
quality of your package.
Thanks for your support and understanding.
9 years, 8 months
Announcing the release of Fedora 20 Alpha!
by Kevin Fenzi
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 expected in early December.
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.)
*** Changes ***
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.
To see how Fedora 20 is evolving from Fedora 19, see the accepted
== 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
== 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 Improvements ===
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 change 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.
* 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: This change will fix running
ARM VMs on x86 hosts using standard libvirt tools libvirt virsh,
virt-manager and virt-install.
== Developer Goodness ==
As always, Fedora 20 will include several new features and updated
packages that will be of interest to all manner of developers.
* Ruby on Rails 4.0: This update will keep Fedora up-to-date and will
ensure that the current Ruby on Rails developers stay with us as they
will get support for system-packaged Ruby on Rails of the latest
version. Apart from that, Rails 4.0 also bring improved
functionality, speed. security and better modularization.
* Perl 5.18: Perl 5.18 will be shipped in Fedora 20. Perl doesn't get
as much attention these days, but it's still a vital part of many
production and development environments. Fedora will deliver the most
up-to-date Perl release so its users will be able to stay current
with the latest Perl.
*** Desktop Environments and Spins ***
= GNOME 3.10 =
Fedora 20 Alpha will have a preview of GNOME 3.10, GNOME 3.9.90. GNOME
3.10 will have a number of new applications and new features that will
please GNOME-lovers in the Fedora 20 release. This release includes a
new music application (gnome-music), a new maps application
(gnome-maps), a revamp for the system status menu, and Zimbra support
There is also preliminary support in this release for running
GNOME-shell as a Wayland compositor, though Wayland may not be in the
default packages for the final Fedora 20 release.
= KDE Plasma Workspaces 4.11 =
The Fedora KDE SIG has rebased to KDE 4.11 for Fedora 20. This release
includes faster Nepomuk indexing, improvements to Kontact, KScreen
integration in KWin, Metalink/HTTP support for KGet, and much more.
= 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, visit the Fedora 20
Release Spins page:
Nightly composes of alternate Spins are available here:
*** 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 the kernel debug strategy
page 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 on the Fedora wiki:
For tips on reporting a bug effectively, read "How to File a Bug
Report:" http://fedoraproject.org/wiki/How_to_file_a_bug_report .
You can join the Fedora QA team mailing list here:
** Contributing ***
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
9 years, 8 months
Reminder on how to EOL a package
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
As the procedure recently changed a little and many people have gotten
it wrong for a long time I wanted to bring to everyones attention the
proper procedure to retire a package that is no longer useful.
its now one step from the CLI assuming you have a new enough fedpkg
installed fedpkg-1.13-1 or newer. many thanks to Till for the
Also please note that you are not to Retire packages for stable
Fedora's we have no way to remove them and If you retire it they will
be in a weird state where the package will be in the repos and
available to install but koji will say its blocked. It will create
confusion for both users and fellow developers. So DO NOT DO IT.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
-----END PGP SIGNATURE-----
9 years, 8 months
Fedora Working Groups: Call for Self-Nominations
by Matthew Miller
Based on discussions at and around Flock, the Fedora Project Board has
approved a proposal for a big change in the way we put Fedora together.
Rather than presenting one Fedora with multiple slightly-different
install options, future Fedora will be designed, developed, and promoted
as three separate products built around a common core.
To take that idea from talk to reality, we're making a corresponding
change to Fedora leadership. Each product will be guided by a Working
Group, which will function as an independent subcommittee of FESCo, (the
Fedora Engineering Steering Committee). FESCo will resolve issues which
impact multiple working groups, and the Fedora Board will continue to
set overall strategic direction, but the working groups will be largely
autonomous within their own areas.
We are creating a group for each of the three initial products the Board
* Fedora Workstation
* Fedora Server
* Fedora Cloud
The Board asks that the Working Groups determine their own target
audience definition and product description as a first task; the names
aren't set in stone.
We're also creating groups to focus on the common core, and to work on
policies and practices for software operating outside of Fedora's
traditional packaging model, alongside the existing (and continuing)
Fedora Packaging Committee.
* Base Design Working Group
* Environments & Software Stacks Working Group
The working groups' initial membership will be chosen by FESCo from
volunteers. This message is the request for those volunteers to
Each group will have at least one FESCo member, who will act as a
liaison to FESCo and as a representative of the group at FESCo meetings.
We would like each group to also have representation from other major
areas of Fedora - Quality Assurance, Infrastructure, Release
Engineering, Documentation, Design, Websites, Ambassadors, Feature
Wrangler, Marketing. We don't intend for this to be additional work to
current members of those teams; working group members should interact
with and augment the existing subprojects.
These working groups will be more formal than the existing SIGs, with a
documented governing structure and process of operation, voting members,
up-to-date and maintained project materials, and regular open
communication. All working group members will need to actively
The first responsibility will be to establish a governance charter,
followed by a product requirements document. We're obviously in the
middle of Fedora 20 development, and that's the priority for many of us
right now. For that reason, these deliverables won't be required until
after the F20 release, but we do want to start organizing as soon as
Interlude: Interested in Something Else?
Are the projects listed above not your interest? That's fine; you can
keep on working the way you are now. Or, perhaps you're interested in a
target product, but something different from the ones described above.
In that case, you may start a "secondary product" working group
following the same model; if that is successful the Fedora Board may
elect to promote that product to a primary target.
How to Self-Nominate
To volunteer to serve on one of the new Fedora working groups, simply
add yourself to the appropriate section in the wiki page below, along
with a brief description of your current involvement with Fedora and
plans for participation in this group.
The nomination period will be at least one month from this announcement.
FESCo will review the applications, appoint the initial members, and
assist with the development of each group's independent governance.
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
9 years, 8 months