= Proposed System Wide Change: perl Package to Install Core Modules =
https://fedoraproject.org/wiki/Changes/perl_Package_to_Install_Core_Modules
Change owner(s):
* Petr Písař <ppisar AT redhat DOT com>
dnf install perl will install all core Perl modules that come with
Perl upstream sources.
== Detailed Description ==
Upstream releases Perl interpreter together many Perl modules. This
set of modules is called core modules. Fedora splits the modules into
subpackages so that installing perl package results in stripped-down
set of modules. Fedora documents this as a feature and provides
perl-core to metapackage that allows installing all the core modules
as is intended by upstream.
Unfortunately this seems to be confusing to Perl users because Fedora
is the only distribution doing so.
To align Fedora's behaviour to upstream and other distributions this
change will rename perl package to perl-interpreter and perl-core
package to perl'. This will allow installing all core Perl modules
with dnf install perl while still retain the possibility to install
only a minimal perl interpreter (/usr/bin/perl) with dnf install
perl-interpreter.
This change will also update Fedora Packaging Guidelines for Perl to
all spec files that require perl to use perl-interpreter instead.
There is only 81 binary packages affected. They will rebuilt.
Otherwise no mass rebuild won't be necessary.
To ease sharing spec files with older Fedoras, perl-interpreter
provide will add to perl package there.
== Scope ==
* Proposal owners:
- Submit Fedora Packaging Guidelines for Perl update to Fedora
Packaging Committee.
- Update and rebuild perl source package.
- Add Provides: perl-interpreter to perl package in older Fedoras.
- Replace BuildRequires and Requires for perl with perl-interpreter in
all spec files.
- Rebuild packages with replaced Requires to propagate the change to
repositories.
- Replace perl-core with perl in compose groups definition.
* Other developers:
Get familiar with new Fedora Packaging Guidelines for Perl.
* Release engineering:
No action needed. Request to check of an impact with Release
Engineering: https://pagure.io/releng/issue/6842
* List of deliverables:
Anything what contains perl package
* Policies and guidelines:
Fedora Packaging Guidelines for Perl update request (
https://pagure.io/packaging-committee/issue/690 ) to use perl and
perl-interpreter instead of perl-core and perl.
Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Hi everyone,
Our hotel discount code for Flock went live yesterday. It is... *drumroll* "FLOCK".
Here are the rates:
- A $139/night* rate per double, queen, or king room is available from August 27 to August 31. You will need to use the "Group Attendee" code "FLOCK" on the hotel reservation form to book your room at the Flock rate.
- A $169/night* double occupancy (under 18 free) discounted rate is available the weekend before and the weekend after (evenings of Fri Aug 25 and Sat Aug 26 + evenings of Fri Sep 1 and Sat Sep 2. The $139 rate is available Thu Aug 24 and Mon Sep 3.)
- If you are booking by phone, please state that you are attending the Flock 2017 Conference.
- July 26 is the cut-off for our reserved block. If reserving for yourself, please book before then!
*IF YOU ARE APPLYING FOR FUNDING DO NOT RESERVE YOUR ROOM.* We'll book it for you if you are funded. :)
The website is updated with this info.
Also, we're looking forward to reviewing your session proposals, which are due tomorrow! :)
For more frequent updates about Flock 2017, please subscribe to:
https://lists.fedoraproject.org/admin/lists/flock-attendees-2017.lists.fedo…
Cheers,
~m
The Fedora Project is pleased to announce the immediate availability
of Fedora 26 Beta, the next big step on our journey to the exciting
Fedora 26 release in July.
Download the prerelease from our Get Fedora site:
* Get Fedora 26 Beta Workstation
https://getfedora.org/workstation/prerelease/
* Get Fedora 26 Beta Server
https://getfedora.org/server/prerelease/
* Get Fedora 26 Pre-Release Atomic
https://getfedora.org/atomic/prerelease/
Looking for Fedora Cloud Base? This is replaced by Atomic as a Fedora
Edition for the container use case, but we still produce it for those
of you who want to build up your own cloud-computing environment in a
more traditional way from https://cloud.fedoraproject.org/.
Or, check out one of our popular variants, including KDE Plasma, Xfce,
and other desktop environments, as well as images for ARM devices
like the Raspberry Pi 2 and 3:
* Get Fedora 26 Beta Spins
https://spins.fedoraproject.org/prerelease
* Get Fedora 26 Beta Labs
https://labs.fedoraproject.org/prerelease
* Get Fedora 26 Beta ARM
https://arm.fedoraproject.org/prerelease
Fedora’s journey is not simply about updating one operating system
with the latest and greatest packages. It’s also about innovation for
the many different platforms represented in the Fedora Project:
Workstation, Server, Atomic, and the various Spins. Coordinating the
efforts across the many working groups is no small task, and serves
as a testament to the talent and professionalism found within the
Fedora community.
As we move into this Beta phase of the Fedora 26 release cycle, what
can users expect?
Fedora-Wide Changes
===================
Fedora, always in the path of innovation, will ship with the latest
version of the GNU Compiler Collection, also known as GCC, bringing
the latest language features and optimizations to users and to the
software we build. Also the Go Language is updated to the latest
version, 1.8, which includes 32-bits MIPS support and speed
improvements.
One of the most important changes is the addition of "blivet-gui" to
the installer. This provides a "building-blocks" style partitioning
GUI for sysadmins and enthusiast users who are familiar with the
details of storage systems.
Also, we've made and included many improvements in security, improving
user experience and reducing the risks of the digital life.
Fedora Editions
===============
The Workstation edition of Fedora 26 Beta features GNOME 3.24, which
includes important changes like Night Light, which changes the color
temperature of the display based on time of day. It will also
include the latest update of LibreOffice.
Our Atomic Host Edition also has a lot of improvements, including
more options to run containers, the latest version of the docker
container platform, the cockpit manager and the atomic CLI, improving
the way containers are managed, making being a sysadmin easier.
Spins and Labs
==============
The Fedora Project is proud to announce two new versions: The LXQt
Spin, a lightweight desktop supporting the latest version of the Qt
libraries; and the Python Classroom Lab, a new version focused in the
teaching and learning of the Python programming language. And, in the
Cinnamon Spin, the desktop is updated to the latest version.
Alternative Architectures
=========================
We are also simultaneously releasing 64-bit F26 Beta for ARM
(AArch64), Power (both little and big endian) and s390x
architectures. You'll also find minimal network installers and the
Fedora 26 Beta Cloud Base image here:
* Get Beta Alternative Architectures and Other Downloads.
https://alt.fedoraproject.org/prerelease/
What is the Beta Release?
=========================
A Beta release is code-complete and bears a very strong resemblance
to the third and final release. The final release of Fedora 26 is
expected in July. If you take the time to download and try out the
Beta, you can check and make sure the things that are important to
you are working. Every bug you find and report doesn’t just help you,
it improves the experience of millions of Fedora users worldwide!
Together, we can make Fedora rock-solid. We have a culture of
coordinating new features and pushing fixes upstream as much as we
can, and your feedback improves not only Fedora, but Linux and Free
software as a whole.
Issues and Details
==================
Since this is a Beta release, we expect that you may encounter bugs
or missing features. To report issues encountered during testing,
contact the Fedora QA team via the mailing list or in #fedora-qa on
Freenode. As testing progresses, common issues are tracked on the
Common F26 Bugs page. https://fedoraproject.org/wiki/Common_F26_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
More information
================
For more detailed information about what's new on Fedora 26 Beta
Release, you can consult our Talking Points and the F26 Change Set.
* https://fedoraproject.org/wiki/Fedora_26_talking_points
* https://fedoraproject.org/wiki/Releases/26/ChangeSet
They contain more technical information about the new packages and
improvements shipped with this release.
= Proposed Self Contained Change: Decouple system java setting from
java command setting =
https://fedoraproject.org/wiki/Changes/Decouple_system_java_setting_from_ja…
Change owner(s):
* Michael Simacek <msimacek AT redhat DOT com>
* Mikolaj Izdebski <mizdebsk AT redhat DOT com>
Alternatives can be used to specify which Java installation should be
the default for the system. Currently, changing the default java
command causes not only a change to the /usr/bin/java symlink, but
also affects the which runtime is used for system installed Java
applications. We propose introduction of separate setting for
system-wide java applications.
== Detailed Description ==
Fedora allows parallel installation of multiple Java runtime
environments and it uses alternatives mechanism to allow the user to
switch between them. JDK packages provide a set of alternatives
symlinks for it's executables. The java symlink is used to determine
the java command (/usr/bin/java), but also determines which runtime
environment is used to run system-wide Java applications installed
from RPMs, such as maven or eclipse. While in theory different Java
runtime environments are drop-in replacements for each other, in
practice some of the applications may stop working properly. Users
usually install alternative JDKs in order to run their own
applications and don't expect that changing the java command will have
effect on the system applications. By introducing a separate setting
for system-wide java, we would avoid this problem. We propose
specifying default Java runtime for RPM-managed applications in
/etc/java/java.conf (this is already possible, but not currently
used). Administrators would still be able to override the system
default if they need to.
== Scope ==
* Proposal owners:
Adjust javapackages-tools to provide default Java setting in /etc/java/java.conf
* Other developers:
N/A (not a System Wide Change)
* Release engineering:
https://pagure.io/releng/issue/6831
* List of deliverables:
N/A (not a System Wide Change)
* Policies and guidelines:
N/A (not a System Wide Change)
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
I just wanted to call out in particular this bit from Jan's note:
> This slip of the F26 release does not have any impact on F27 schedule [3].
> [3] https://fedoraproject.org/wiki/Releases/27/Schedule
This means that system-wide changes for Fedora 27 should be submitted
to FESCo *before* the Fedora 26 final release. Changes which require a
mass rebuild should be in _this_ month.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
= Proposed Self Contained Change: Node.js 8.x =
https://fedoraproject.org/wiki/Changes/NodeJS8x
Change owner(s):
* Zuzana Svetlikova <zsvetlik AT redhat DOT com>
Fedora 27 will be updated to Node.js 8.x, the latest LTS release of
the platform built on Chrome's JavaScript runtime for easily building
fast, scalable network applications.
== Detailed Description ==
Node.js has seen many changes between v6.x and v8.x. Note that this
release includes API updates that may require dependency updates.
Upstream maintains an exhaustive list of interesting changes here:
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md
Node.js 8.x will be under active development until October 2017, at
which time it will enter its long-term stable release, which will be
maintained actively through April 2019 and for security issues until
December 2019.
== Scope ==
Proposal owners:
- Update nodejs
- Rebuild all binary modules, apply patches as necessary
* Other developers:
Other Node.js packagers' attention may be required if the update
causes issues for their packages.
* Release engineering:
N/A
* Policies and guidelines:
No expected changes
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic