F21 System Wide Change: GNOME 3.12
by Jaroslav Reznik
= Proposed System Wide Change: GNOME 3.12 =
https://fedoraproject.org/wiki/Changes/GNOME3.12
Change owner(s): Matthias Clasen <mclasen(a)redhat.com >
Responsible WG: Workstation
Update GNOME to the latest upstream release. Depending on the Fedora 21
schedule, this might be GNOME 3.12 or 3.14.
== Detailed Description ==
The new features for GNOME 3.12 include:
* More complete hi-dpi support
* gnome-software better integrated
* totem is now Videos
* New applications:
** gnome-logs: A systemd journal viewer
** gnome-sound-recorder: A simple utility for audio recordings
** polari: A irc client
* Google cloud print support
* Windows live email support
* A terminal search provider
The Wayland port of GNOME is still a preview in 3.12.
The feature set for GNOME 3.14 has not been determined yet.
== Scope ==
* Proposal owners:
** Keep existing GNOME packages updated
** Follow upstream module changes
** Package new applications and new dependencies of existing GNOME packages
*** gnome-logs (Done)
*** gnome-sound-recorder (Done)
*** polari (Done)
* Other developers:
** Package new dependencies:
*** libinput (Done)
* Release engineering:
** Extract app data for gnome-software during package builds and provide it in
repositories
* Policies and guidelines:
** Add app data expectations to packaging guidelines
10 years
F21 System Wide Change: Fedora 21 Boost 1.56 Uplift
by Jaroslav Reznik
= Proposed System Wide Change: Fedora 21 Boost 1.56 Uplift =
https://fedoraproject.org/wiki/Changes/F21Boost156
Change owner(s): Petr Machata <pmachata redhat com> with backup contact, co-
maintainer Denis Arnaud
This change brings Boost 1.56.0 (or, failing that, Boost 1.55.0) to Fedora 21.
== Detailed Description ==
The aim is to synchronize Fedora with the most recent Boost release. Because
ABI stability is one of explicit Boost non-goals, this entails rebuilding of
all dependent packages. This has also always entailed yours truly assisting
maintainers of client packages in decoding cryptic boostese seen in output
from g++. Such care is to be expected this time around as well.
Boost 1.56 doesn't have firm schedule yet. Current provisional schedule
(published at [1]) talks about May 5 2014, which would give us enough time to
package Boost 1.56. But we may have to package Boost 1.55 instead.
Here is the Fedora 20 Change [2], should you need it.
== Scope ==
Rebasing Boost has a fairly large impact on Fedora. For Fedora 20, the scope
was: about 130 packages _must_ be rebuilt due to ABI breakage inherent in
bumping Boost sonames. There were almost 250 client packages total. I expect
these numbers to stay largely the same for Fedora 21.
* Proposal owners:
** Build will be done with Boost.Build v2 (which is upstream-sanctioned way of
building Boost)
** Request a "boost" build system tag ([3]) (tag request ticket[4])
** Build boost into that tag (e.g., build [5])
** Post a request for rebuilds to fedora-devel (e.g., message [6])
** Work on rebuilding dependent packages in the tag.
** When most is done, re-tag all the packages to rawhide
** Watch fedora-devel and assist in rebuilding broken Boost clients (by fixing
the client, or Boost).
* Other developers: Those who depend on Boost DSO's will have to rebuild their
packages. Feature owners will alleviate some of this work as indicated above,
and will assist those whose packages fail to build in debugging them.
* Release engineering: Side tag creation.
* Policies and guidelines: Apart from scope, this is business as usual, so no
policies, no guidelines.
[1] https://groups.google.com/forum/#!topic/boost-devel-archive/iwJ-GvtkDlg
[2] https://fedoraproject.org/wiki/Changes/F20Boost154
[3] http://lists.fedoraproject.org/pipermail/devel/2011-November/159908.html
[4] https://fedorahosted.org/rel-eng/ticket/5691
[5] http://koji.fedoraproject.org/koji/buildinfo?buildID=344226
[6] https://lists.fedoraproject.org/pipermail/devel/2012-July/170272.html
10 years
Summary of accepted Fedora 21 Changes - weeks 13/14
by Jaroslav Reznik
Greetings!
This is a summary of FESCo's accepted Fedora 21 Changes for weeks 13 and 14
(2014-03-26 and 2014-04-02 meetings).
Reminder: the Change Submission deadline for System Wide Change is
tomorrow (2014-04-08 23:59 UTC).
=Accepted changes=
== System Wide Changes ==
* Modular Kernel Packaging for Cloud
URL:
https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196807.html
Kernel modules that are not necessary in virtualized environments become
optionally (un)installable.
* Optional Javadocs
URL: https://fedoraproject.org/wiki/Changes/OptionalJavadocs
Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196808.html
Make javadoc subpackages of Java packages optional in guidelines and
communicate this change to users.
* Ruby on Rails 4.1
URL: https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.1
Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196803.html
Ruby on Rails 4.1 is the latest version of well know web framework written in
Ruby.
* Java 8
URL: https://fedoraproject.org/wiki/Changes/Java8
Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196962.html
Make Java 8 (provided by OpenJDK 8 which is java-1.8.0-openjdk) the default
Java runtime. The current default Java runtime (Java 7, provided by OpenJDK 7,
java-1.7.0-openjdk) will be obsoleted and removed.
This is essentially an upgrade to the latest Java and OpenJDK version.
* PrivateDevices=yes and PrivateNetwork=yes For Long-Running Services
URL:
https://fedoraproject.org/wiki/Changes/PrivateDevicesAndPrivateNetwork
Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/197175.html
Let's make Fedora more secure by default! Recent systemd versions provide two
per-service switches PrivateDevices?=yes/no and PrivateNetwork?=yes/no which
enable services to run without access to any physical devices in /dev, or
without access to kind of network sockets. So far this has seen little use in
Fedora, and with this Fedora Change we'd like to change this, and enable these
for all long-running services that do not require device/network access.
notting has question to note: is disconnecting the netlink and audit namespace
truly required, or just merely a choice of what they decided to remove?
== Self Contained Changes ==
* Amplab Tachyon - https://fedoraproject.org/wiki/Changes/AmplabTachyon
discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197168.html
Amplab-Tachyon is a fault tolerant distributed file system enabling reliable
file sharing at memory-speed across cluster frameworks.
* Apache Mesos - https://fedoraproject.org/wiki/Changes/ApacheMesos discussed
at https://lists.fedoraproject.org/pipermail/devel/2014-March/197180.html
Apache Mesos is a cluster manager for sharing distributed application
frameworks. This change brings Mesos to Fedora, which many have called a
micro-kernel for the data center.
* Apache Spark - https://fedoraproject.org/wiki/Changes/ApacheSpark discussed
at https://lists.fedoraproject.org/pipermail/devel/2014-March/196967.html
Apache Spark is a fast and general engine for large-scale data processing.
This change brings Spark to Fedora, allowing easy deployment and development
of Spark applications on Fedora.
* Improved Scala Ecosystem Support -
https://fedoraproject.org/wiki/Changes/ImprovedScalaEcosystem discussed at
https://lists.fedoraproject.org/pipermail/devel/2014-March/196964.html
Fedora now supports several essential parts of the Scala language ecosystem as
well as building packages with sbt, the de facto build tool for the Scala
community.
Scala proposal owners to work to develop packaging guidelines
* DNSSEC support for FreeIPA -
https://fedoraproject.org/wiki/Changes/IPAv3DNSSEC discussed at
https://lists.fedoraproject.org/pipermail/devel/2014-March/197177.html
FreeIPA with integrated DNS server will support serving of DNSSEC secured
zones and automatic DNSSEC key maintenance.
This first version will have only the very basic functionality with limited
user interface and limited resiliency. Next versions (to be delivered in
Fedora 22 time frame) will improve resiliency and user interface
significantly.
* NFS Ganesha File Server - https://fedoraproject.org/wiki/Changes/NFSGanesha
discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196968.html
NFS Ganesha is a user mode file server that supports NFSv3, NFSv4, and NFSv4.1
including pNFS for distributed filesystems. It uses loadable filesystem driver
modules to support its backend filesystems. It also integrates 9P.2000L file
service
= Rejected Changes =
* Security Policy In The Installer
URL: https://fedoraproject.org/wiki/Changes/SecurityPolicyInTheInstaller
Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196666.html
There are many known tips and tricks how to make a system more secure, often
depending on the use case for the system. With the OSCAP Anaconda Addon and
the SCAP Security Guide projects, we may allow users choosing a security
policy for their newly installed system.
Please consider re-proposing as a kickstart-only change.
10 years
F21 Self Contained Change: MATE Desktop 1.8
by Jaroslav Reznik
= Proposed Self Contained Change: MATE Desktop 1.8 =
https://fedoraproject.org/wiki/Changes/MATE_1.8
Change owner(s): Dan Mashal <dan.mashal(a)fedoraproject.org>, Wolfgang Ulbrich
<chat-to-me(a)raveit.de>
Update MATE Desktop to version 1.8
== Detailed Description ==
Release 1.8
* New features
- new mate-user-quide
- add window snapping/tiling support to Marco window-manager
- improved support for systemd-logind
- command line panel-applet for displaying the result of a command in the
panel
- mpaste tool for using Mate's paste website
- caja-beesu extension for opening a file as superuser
- support for upower-1.0 (60% is done in rawhide)
- allow rotation of mate-panel background
- add support for Metacity as window manager
- add shuffle mode in slideshow of eom image-viewer
- eom image-viewer is migrated to lcms2
- show date and time in mate-screensaver lock dialog
- show graphical time in logout/shutdown dialog
- switch complete to pulseaudio, good bye gstreamer mixer
- middle click on volume-applet toggles mute state
- add undo functionality to Sticky-note applet
- gnome-main-menu panel-applet (review request comming soon)
* Renaming some packages
- mate-file-manager to caja
- mate-window-manager to marco
- mate-text-editor to pluma
- mate-document-viewer to atril
- mate-menu-editor to mozo
- mate-file-archiver to engrampa
- mate-image-viever to eom
* Replacements
- mate-doc-utils with yelp-tools, help in all packages works now
- single caja extensions packages are now summarized in the new caja-
extensions package
- libmatewnck with libwnck
* Drops
- mate-character-maps
== Scope ==
* Proposal owners:
1) Upgrade all packages to 1.8 version.
2) Update comps with new package set.
3) Submit review requests for the following renamed packages:
mate-file-manager -> caja
mate-window-manager -> marco
mate-image-viewer -> eom
mate-file-archiver -> engrampa
mate-text-editor -> pluma
mate-document-viewer -> atril
mate-menu-editor -> mozo
4) Retire the following dropped packages:
libmatewnck
mate-doc-utils
mate-keyring
* 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)
10 years
F21 System Wide Change: RPM-4.12
by Jaroslav Reznik
= Proposed System Wide Change: RPM-4.12 =
https://fedoraproject.org/wiki/Changes/RPM-4.12
Change owner(s): Florian Festi, Panu Matilainen <rpm-maint(a)rpm.org>
Update RPM to the upcoming 4.12 release.
== Detailed Description ==
The current upstream repository contains several improvements that need to get
released and integrated into Fedora:
* Support for weak dependencies
* Support for packaging files > 4GB
* Support for real package reinstallation
* New API for accessing files and file contents
* New tool for converting rpm packages to tar files
* Internal plugin interface
* Massive code clean ups
* Many bug fixes
Some of these features require the new version to reach the builders. So
actually introducing them in Fedora will take longer that the Fedora 21
release. Nevertheless updating RPM in F21 is the first step to make this
happen.
== Scope ==
* Proposal owners: The RPM code base needs to get stabilized and release
ready. The release candidates need to be tested in rawhide.
* Other developers: Will test the release candidates during normal operation
in raw hide. Need to report issues and bugs.
* Release engineering: Have a look for compatibility issues.
* Policies and guidelines: Packaging policies might need reconsidering in the
light of the new options (F22 or even F23 time frame).
10 years
F21 System Wide Change: lbzip2 as default bzip2 implementation
by Jaroslav Reznik
= Proposed System Wide Change: lbzip2 as default bzip2 implementation =
https://fedoraproject.org/wiki/Changes/lbzip2
Change owner(s): Mikolaj Izdebski <mizdebsk(a)redhat.com>
This change aims at making lbzip2 [1] default bzip2 implementation used in
Fedora.
== Detailed Description ==
lbzip2 is an independent implementation of bzip2 compression tool. It provides
interface strictly compatible with bzip2, but also adds several new features
and improvements, such as:
* multi-threaded operation for both compression and decompression, with almost
linear scalability,
* improved performance, even on single-core systems,
* improved extra utilities (bzdiff, bzless, bzip2recover, etc.),
* improved compatibility with gzip.
lbzip2 is a mature project and it has been used in production for years. It is
already packaged for Fedora and it is also available in EPEL.
The case of bzip2 and lbzip2 is an ideal candidate for usage of alternatives -
both tools provide commands with compatible interfaces. This change proposes
assigning higher priority to lbzip2 than to bzip2, which will effectively
cause lbzip2 to be used instead of bzip2, if lbzip2 is installed. If for some
reason some users don't like the change they can reconfigure alternatives
manually and keep using bzip2.
== Scope ==
* Proposal owners:
** make lbzip2 and bzip2 packages use alternatives for binaries and manpages
they provide,
** set higher priority for lbzip2 in alternatives,
** identify packages which require bzip2 and port some of them to use lbzip2
instead.
* Other developers:
** test if their packages work with lbzip2,
** possibly adjust spec files to require or build-require lbzip2 instead of
bzip2.
* Release engineering: no action required.
* Policies and guidelines: no change required.
[1] http://lbzip2.org/
10 years
F21 System Wide Change: GHC 7.8
by Jaroslav Reznik
= Proposed System Wide Change: GHC 7.8 =
https://fedoraproject.org/wiki/Changes/GHC_7.8
Change owner(s): Jens Petersen <petersen(a)redhat.com>, Ricky Elrod
<relrod(a)redhat.com>, Haskell_SIG <haskell(a)lists.fedoraproject.org>
Update the GHC Haskell compiler to the major new 7.8 release, and
update/rebuild all Haskell packages against it.
== Detailed Description ==
* The involves updating ghc from 7.6.3 to 7.8.1 (or later), and
rebuilding/updating all Fedora Haskell packages.
* The initial work will be done locally offline to make sure that it is
possible to build all our packages with ghc-7.8 and the latest updated
libraries.
* This may also include building with the llvm backend to ensure that building
on ARM will work.
* Once that is completed, building will be done into Koji for rawhide and
testing done.
== Scope ==
* Proposal owners:
** locally test rebuilding and updating of all packages
** update macros to subpackage static libraries
** push changes to Koji
** testing
* Other developers: If you own a package which contains some Haskell code
built with ghc you will need to rebuild you package to make sure it still
rebuilds with ghc-7.8. Feel free to contact the Haskell SIG if we need
assistance with fixing any build breakage, and we will try to help out.
* Release engineering: not required
* Policies and guidelines: There may be some lesser changes to the Haskell
Packaging Guidelines needed - they could be done after this Change.
10 years
F21 Self Contained Change: KDE Frameworks 5
by Jaroslav Reznik
= Proposed Self Contained Change: KDE Frameworks 5 =
https://fedoraproject.org/wiki/Changes/KDE_Frameworks_5
Change owner(s): Daniel Vrátil <dvratil(a)redhat.com>
KDE Frameworks 5 is a set of libraries and technologies developed in the KDE
project over the past 18 years. Most of the frameworks come from the kdelibs
module, which has been split, cleaned up, dependencies were strightened and
packed into individual libraries. This allows developers and projects outside
the KDE ecosystem to make use of these technologies and benefit from work of
the KDE Community.
== Detailed Description ==
KDE Frameworks 5 is the successor to KDE Platform 4, bringing significant
technical differences and a change in focus. It will be the first release of
KDE libraries based on Qt 5, which brings significant improvements to users.
New technologies are being introduced and libraries are being cleaned up,
reviewed and brought up to date with new standards. At the same time, the team
is making the development platform more modular and making it easier to reuse
solutions in a wider range of platforms and devices, including desktop and
mobile. Technologies such as QML allow KDE developers to take advantage of a
leading graphics rendering engine, and allow for more organic and fluid user
interfaces across devices.
An important goal of KDE Frameworks 5 is to bring the benefits of KDE
technology to Qt5 users outside the KDE Community. Libraries are split into
distinct components, making it possible for Qt developers to take components
without dragging in other unnecessary libraries. (from [1])
KDE Frameworks 5 don't provide any UI or applications on their own, but are
meant as extensions and addons for the Qt toolkit. In future there will be
various desktop shells like Plasma 2 and applications built on top of KDE
Frameworks 5 providing the full-featured KDE desktop ("KDE 5").
All Frameworks are co-installable with current all KDE 4 packages.
== Scope ==
* Proposal owners: All frameworks are already packaged and are currently
provided in a COPR repository [2]. We only need to have all the packages
reviewed and submit them into Fedora. Given the amount of frameworks
(currently 60), this will take some time to process. This is a completely
isolated change that will not affect any other packages or changes.
* 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)
[1] http://dot.kde.org/2013/09/04/kde-release-structure-evolves
[2] http://copr.fedoraproject.org/coprs/dvratil/kde-frameworks/
10 years