This page lists all of the writing beats for the release notes, and who is assigned to them.
Beat writers should be subscribed to the content flow mailing list.
- + == Ready for conversion to XML
- 0 == Not ready for conversion to XML
- - == Not including in conversion to XML
Fedora Release Notes Beats
Content in the beats may be derived from bugzilla reports and mailing list discussions.
Each beat has one or more beat writers, as assigned on the release notes beats page. The beat writer(s) are in charge of the beat pages. These pages are open for all to contribute. If you know something that should be in the release notes, this is the place to put it.
Writers can learn about how this works on the Docs/Beats/HowTo page.
The page Docs/Beats uses a Wiki include that pulls in the content from the separate beat pages. The actual beat page is located at Docs/Beats/Beatname.
The current version we are writing for is Fedora Final.
Interested in contributing? Read DocsProject/Join.
If you feel a beat is missing, put it in where you think it fits best, and the editors will work with you from there.
Below are all the beats on one page. Use the links from the Table of Contents above to go directly to beat pages.
- REDIRECT Documentation Boot Beat
The following sections contain information regarding software packages that have undergone significant changes for Fedora 11. For easier access, they are generally organized using the same groups that are shown in the installation system.
GDM on Wayland
The Gnome Display Manager (GDM) in Fedora 22 will default to the Wayland display server instead of Xorg. While the default GNOME session still uses X, this change brings the move to Wayland one step closer.
Wayland is a compositing display server, using your computer's video hardware for rendering. On systems where Wayland will not run, GDM should transparently fall back to using the X backend.
If you need to disable Wayland for GDM, edit /etc/gdm/custom.conf to reflect the following:
Libinput used for input devices
Input devices in supporting environments, notably GNOME with Fedora Workstation and KDE, will use a new driver, libinput. The new driver replaces a variety of drivers, such as synaptics, enabling more consistent behavior across a variety of devices.
'libinput improves support for multi-touch devices and software emulated buttons. The driver is implemented directly in wayland sessions, and in X sessions through the xorg-x11-drv-libinput wrapper.
Input devices will be configurable through GNOME Settings, KDE System Settings, xfce-settings, or xinput. Some niche features are not available via libinput, but the previous behavior can be restored by removing the xorg-x11-drv-libinput package, and ensuring the appropriate x11 driver packages, probably x11-drv-synaptics or xorg-x11-drv-evdev are installed.
Note that xorg-x11-drv-libinput is only installed by default on new Fedora 22 installations, if you're upgrading and you want to use the new features provided by libinput, you can install xorg-x11-drv-libinput manually by doing:
sudo dnf install xorg-x11-drv-libinput
To learn about the features and behavior of libinput, refer to `man libinput` or http://wayland.freedesktop.org/libinput/doc/latest/pages.html
yum replaced by dnf
The `yum` package manager has been replaced in Fedora 22 by its successor, dnf. The yum fork has been available in Fedora for testing since Fedora 18, and is now the default command line package manager.
Most dnf commands use directives that are familiar to yum users, and it uses the same RPM package repositories. Behind the scenes, dnf uses an improved dependency solver, `hawkey`, along with `librepo` for repository operations and `libcomps` for package groups.
The behavior of dnf differs from yum in some areas:
Updates that don't work are skipped
If a portion of a transaction is not viable, dnf will automatically exclude it and transparently continue with the portions that will work. For example, if a package has unmet dependencies during a `dnf update` action, that package will not be updated, but others will. This is similar to yum's "--skip-broken" directive, but evaluates the impact of the problem against the entire transaction. Because this is the default behavior, there is no "--skip-broken" switch for dnf.
To review details about a problematic package direction, you can use the "--best" option. `dnf update --best` will force dnf to resolve the transaction using the latest versions of involved packages, and report any problems instead of skipping them.
Repos that don't work are skipped
If a configured and enabled repository does not respond, dnf will skip it and continue the transaction with the available repos. This differs from yum, which would immediately stop if a repository was not available.
Update and Upgrade are the same
The commands `dnf update` and `dnf upgrade` are equivalent. This differs from yum, where `yum upgrade` would have the same effect as `yum update --obsoletes`, and take obsolete packages into account.
Dependencies are not upgraded on package installation
When installing a new package, previously installed dependencies will not be upgraded. Yum offered an option for this behavior, upgrade_requirements_on_install. To upgrade with dnf, use `dnf update`.
Clean on remove
When removing a package, dnf will automatically remove any dependent packages that were not explicitly installed by the user. If a package was independently installed, it won't be uninstalled this way.
This behavior is configured by the "clean_requirements_on_remove" option in /etc/dnf/dnf.conf.
Repo cache refresh schedule
By default, dnf will check for updates in configured repositories hourly, starting ten minutes after the system boots. The action is controlled by a systemd timer unit, /usr/lib/systemd/system/dnf-makecache.timer.
To adjust this, copy the timer file to /etc/systemd/system/dnf-makecache.timer and edit it.
Alternatively, setting the metadata_timer_sync in /etc/dnf/dnf.conf to a number of seconds configures the minimum number of seconds between makecache operations. If the timer has not expired, `dnf makecache` will exit immediately.
dnf will also honor the metadata_expire option set in individual repo configs, and refresh repo metadata at runtime if it is too old. This option is described in `man yum.conf`.
Repository Actions =
The "repository-packages" directive can be used to search for or get info about packages in a specific repository, list installed packages frrom that repository, and more. This simplifies operations that would have required use of "--excluderepo" and "--includerepo" options with yum, and is especially useful for managing similar packages from different repositories.
To find out what package supplies a particular provide, use the `dnf provides foo` command. This replaces `yum resolvedep foo`.
To list the dependencies of a package, use `dnf repoquery --requires foo`. This replaces `yum deplist foo`.
dnf will remove kernels
kernel packages are not protected by dnf. Unlike with yum, you can remove all kernel packages, including the running package, if you direct it to. Be cautious with removing kernels, and specify the full package and version
When a system requires the capabilities of a package you want to replace, use the --allowerasing option. For example, `dnf --allowerasing mariadb` will allow you to replace mysql with mariadb, without disrupting packages that require capabilities provided by both packages. This replaces `yum shell` and `yum swap` functionality.
- Upstream documentation at http://dnf.readthedocs.org/en/latest/index.html
- Plugins documented at https://rpm-software-management.github.io/dnf-plugins-extras/index.html
The Berkeley Internet Name Domain (BIND) has been updated to version 9.10. This version adds IPv6 listening by default. It also unifies external and internal libraries so that external applications can use the same libraries as BIND daemons. The version 3 XML schema, which provides faster parsing, is no longer optional.
Fedora uses `chronie` for execution of scheduled tasks using the `chrond` service. Packages may drop files into /etc/cron.d/ to add a task, or a user can add a task using the `crontab` utility.
To learn about using cron jobs, refer to:
- `man 1 crontab`
- `man 5 crontab`
- `man 8 cron`
- `man 8 crond`
- This page will be changing as more information comes available.
- Information Current as of Fedora 22 Alpha 3
Available in Fedora 22 and returning from Fedora 21:
- RythmBox: Version 3.1-1.fc22 (Audio Player capable of being a podcast/netcast catcher)
- Videos: Version 1:3.15.90-1.fc22 Video Player included in Fedora
- Cheese: Version 2:3.15.90-1.fc22 Video and snapshot app that uses your webcam
- Weather: Version 3.15.90-1.fc22 Integrated Weather Application for your Desktop
- None installed by default but titles can be downloaded for free from the Software app.
In Fedora 22, the postgresql packages have been updated to the upstream version 9.4.1, which provides various bug fixes and enhancements described on upstream 9.4.0 release notes and 9.4.1 release notes pages.
Migration to new PostgreSQL version may be done by running of the post-upgrade script
postgresql-setup (meaning that you may firstly update your Fedora installation from version 21 to 22 and then perform database stack update). Users are encouraged to do full database dump (for backup purposes) before Fedora upgrade to 22. For more info about migration look into the
README.rpm-dist file distributed in
System locale and keyboard layout settings are configured using the `localectl` utility. Read `man localectl` for instructions on adjusting the system locale.
- New Fonts
- google-noto-sans-oriya-fonts, google-noto-sans-oriya-ui-fonts
This list is generated for the release and posted on the wiki only. It is made using the
repodiff utility from the
yum-utils package, ran as
repodiff --old=<base URL of the old SRPMS repository> --new=<base URL of the new SRPMS repository>.
For a list of which packages were updated since the previous release, refer to http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/UpdatedPackages. You can also find a comparison of major packages between all Fedora versions at http://distrowatch.com/fedora.
Insert repodiff list here.
- Fedora 11 includes bash 4.0
The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from free and open source software. The Fedora Project is driven by the individuals that contribute to it. As a tester, developer, documenter, or translator, you can make a difference. Refer to http://join.fedoraproject.org for details. For information on the channels of communication for Fedora users and contributors, refer to http://fedoraproject.org/wiki/Communicate.
In addition to the website, the following mailing lists are available:
- firstname.lastname@example.org, for users of Fedora releases
- email@example.com, for testers of Fedora test releases
- firstname.lastname@example.org, for developers, developers, developers
- email@example.com, for participants of the Documentation Project
To subscribe to any of these lists, send an email with the word "subscribe" in the subject to <listname>-request, where <listname> is one of the above list names. Alternately, you can subscribe to Fedora mailing lists through the Web interface at http://www.redhat.com/mailman/listinfo/.
The Fedora Project also uses several IRC (Internet Relay Chat) channels. IRC is a real-time, text-based form of communication, similar to Instant Messaging. With it, you may have conversations with multiple people in an open channel, or chat with someone privately one-on-one. To talk with other Fedora Project participants via IRC, access the Freenode IRC network. Refer to the Freenode website at http://www.freenode.net/ for more information.
Fedora Project participants frequent the
#fedora channel on the Freenode network, while Fedora Project developers may often be found on the
#fedora-devel channel. Some of the larger projects may have their own channels as well. This information may be found on the webpage for the project, and at Communicate.
In order to talk on the
#fedora channel, you need to register your nickname, or nick. Instructions are given when you
/join the channel.
As we use the term, a colophon:
- recognizes contributors and provides accountability, and
- explains tools and production methods.
- Alain Portal (translator - French)
- Amanpreet Singh Alam (translator - Punjabi)
- Andrew Martynov (translator - Russian)
- Andrew Overholt (beat contributor)
- Anthony Green (beat writer)
- Brandon Holbrook (beat contributor)
- Bob Jensen (beat writer)
- Chris Lennert (beat writer)
- Dale Bewley (beat writer)
- Dave Malcolm (beat writer)
- David Eisenstein (beat writer)
- David Woodhouse (beat writer)
- Deepak Bhole (beat contributor)
- Diego Búrigo Zacarão (translator)
- Dimitris Glezos (beat writer, translator - Greek)
- Domingo Becker (translator - Spanish)
- Fabian Affolter (translator - German)
- Francesco Tombolini (translator - Italian)
- Gavin Henry (beat writer)
- Geert Warrink (translator - Dutch)
- Guido Grazioli (translator - Italian)
- Hugo Cisneiros (translator - Brazilian Portuguese)
- Igor Miletic (translator - Serbian)
- Jason Taylor (beat writer, editor-in-training)
- Jeff Johnston (beat contributor)
- Jesse Keating (beat contributor)
- Jens Petersen (beat writer)
- Joe Orton (beat writer)
- José Nuno Coelho Pires (translator - Portuguese)
- Josh Bressers (beat writer)
- Karsten Wade (beat writer, editor, co-publisher)
- Kevin Kofler (beat writer)
- Kyu Lee (beat contributor)
- Lenka Čelková (translator - Slovak)
- Licio Fonseca (translator - Brazilian Portuguese)
- Lubomir Rintel (beat contributor, translator - Slovak)
- Luya Tshimbalanga (beat writer)
- Magnus Larsson (translator - Swedish)
- Marek Mahut (translator - Slovak)
- Mathieu Schopfer (translator - French)
- Matthieu Rondeau (translator - French)
- Maxim Dziumanenko (translator - Ukrainian)
- Martin Ball (beat writer)
- Nikos Charonitakis (translator - Greek)
- Orion Poplawski (beat contributor)
- Panagiota Bilianou (translator - Greek)
- Patrick Barnes (beat writer, editor)
- Paul W. Frields (tools, editor)
- Pavol Šimo (translator - Slovak)
- Pawel Sadowski (translator - Polish)
- Patrick Ernzer (beat contributor)
- Piotr Drąg (translator - Polish)
- Rahul Sundaram (beat writer, editor)
- Sam Folk-Williams (beat writer)
- Sekine Tatsuo (translator - Japanese)
- Simos Xenitellis (translator - Greek)
- Steve Dickson (beat writer)
- Teta Bilianou (translator - Greek)
- Thomas Canniot (translator - French)
- Thomas Graf (beat writer)
- Tommy Reynolds (tools)
- Valnir Ferreira Jr. (translator - Brazilian Portuguese)
- Ville-Pekka Vainio (translator - Finnish)
- Will Woods (beat contributor)
- Yoshinari Takaoka (translator, tools)
- Yuan Yijun (translator - Simplified Chinese)
- Zhang Yang (translator - simplified Chinese)
...and many more translators. Refer to the Web-updated version of these release notes as we add translators after release:
Beat writers produce the release notes directly on the Fedora Project Wiki. They collaborate with other subject matter experts during the test release phase of Fedora to explain important changes and enhancements. The editorial team ensures consistency and quality of the finished beats, and ports the Wiki material to Doc
Book XML in a revision control repository. At this point, the team of translators produces other language versions of the release notes, and then they become available to the general public as part of Fedora. The publication team also makes them, and subsequent errata, available via the Web.