= Proposed System Wide Change: Python 3.5 =
https://fedoraproject.org/wiki/Changes/python3.5
Change owner(s):
* Robert Kuska <rkuska at redhat dot com>
* Matej Stuchlik <mstuchli at redhat dot com>
Update the Python 3 stack in Fedora from Python 3.4 to Python 3.5.
== Detailed Description ==
Python 3.5 adds numerous features and optimizations. See the upstream
notes at What's new in 3.5.
== Scope ==
As Python3.5 was already released as a final release and Debian had
already updated their Python to v3.5 we could expect all the core
(most used) Python modules to be already Python3.5 compatible.
There is 973 packages that (Build)Requires python3 (in F24). Also it
is important to note that Python3 is now the default interpreter for
Fedora therefore it is crucial part of the distribution (anaconda and
dnf run on Python).
* Proposal owners:
** Make a request to create a f24-python3 side-tag for Python3.5 rebuild.
** Rebuild gdb without python3 support to have minimal buildroot
python3 free as we can't have (currently) simultaneously installed
both Python3.4 and Python3.5 versions within the buildroot.
** Build Python3.5.
** Rebuild gdb and all the packages marked as core within this tag. We
consider all packages shipped by default (and their dependencies) on
Fedora DVD to be core packages.
** Rebuild rest of the packages in mass rebuild
* Other developers:
Owners of packages that fail to rebuild will be asked using bugzilla
to fix or remove their packages from the distribution. They can
rebuild their packages themselves if interested using fedpkg build
--target f24-python3. We will keep the list of rebuilt
packages/packages in queue publicly accessible.
* Release engineering:
Mass rebuild rest of the packages.
* Policies and guidelines:
None
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Fedora 23 Beta Release Announcement for AARCH64 and POWER architectures
=======================================================================
The Fedora 23 Beta is here for AARCH64 and POWER architectures, right
on schedule for our planned October final release! Want to help make
Fedora 23 be the best release ever on those architectures, or just
want to get a sneak peek? Download the prerelease from the site
and give it a whirl:
* Get Fedora 23 Beta Server — make use of the very latest
server-based technologies available in the open source community
https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/23_Beta/Ser…
* Get Fedora 23 Beta Cloud — build scale-out computing and utilize
the next generation of container deployment technology
https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/23_Beta/Clo…
What is the Beta release?
-------------------------
The Beta release contains all the exciting features of Fedora 23's
editions 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 23 is expected
in October.
We need your help to make Fedora 23 the best yet, so please take
some time to download and try out the Beta 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 rock-solid. 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.
Fedora-Wide Changes
-------------------
Fedora 23 includes a number of changes that will improve all of the
editions. For example, Fedora 23 makes use of compiler flags to
improve security by "hardening" the binaries against memory
corruption vulnerabilities, buffer overflows, and so on. This is a
"behind the scenes" change that most users won't notice through
normal use of a Fedora edition, but will help provide additional
system security.
Likewise, Fedora 23 has disabled SSL3 and RC4 by default due to
known vulnerabilities in the protocols. This means all applications
that use GNUTLS and OpenSSL libraries have had the SSL3 protocol
and RC4 cipher disabled.
Fedora 23 Beta also includes support for Unicode 8.0, which
includes new emojis, and improvements in sorting Unicode text and
processing non-ASCII URLs.
Fedora Server
-------------
The Fedora Server release includes a number of interesting changes
and additions.
The rolekit service now supports setting up three roles. In
addition to the previously supported Domain Controller (powered by
FreeIPA abd Database Server (powered by PostgreSQL) roles, Fedora
Server 23 features a cache server for web applications (powered by
memcached).
Rolekit can also now be used from the anaconda kickstart by passing
the `--deferred` arguments to `rolectl`. For example: `rolectl
deploy domaincontroller --name=example.com --deferred` will
instruct the system to deploy the Domain Controller role on the
next boot.
The Cockpit Admin Interface in Fedora Server has several big
improvements as well.
* Support for SSH key authentication
* Support for configuring user accounts with their authorized keys.
* Basic cluster dashboard for driving Kubernetes on Fedora Server
and Fedora Atomic Host.
* Set the imezone for your Fedora Server from the Cockpit User
Interface (UI).
* Cockpit has also been made safe to use with multipath disks.
Fedora Cloud
------------
Fedora 23 Cloud Base image includes many updates and enhancements to the
underlying Fedora base packages. For example, Fedora 23 now has the
latest Docker release, docker 1.8. We can now verify the publisher
of an image before running. This gives the users the power to identify
that the image publisher published has not been tampered with.
Issues and Details
------------------
This is an Beta release. As such, 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 F23
Bugs page. https://fedoraproject.org/wiki/Common_F23_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
Release Schedule
----------------
The full release schedule planned is available on the Fedora wiki.
The current schedule calls for a beta release towards the end of
September, and the final release scheduled towards the end of October.
https://fedoraproject.org/wiki/Releases/23/Schedule
These dates are subject to change, pending any major bugs or issues
found during the development process.
Fedora 23 Beta Release Announcement
===================================
The Fedora 23 Beta is here, right on schedule for our planned
October final release! Want to help make Fedora 23 be the best
release ever, or just want to get a sneak peek? Download the
prerelease from our Get Fedora site and give it a whirl:
- Get Fedora 23 Beta Workstation — a reliable, user-friendly, and
powerful operating system for your laptop or desktop computer
https://getfedora.org/en/workstation/prerelease/
- Get Fedora 23 Beta Server — make use of the very latest
server-based technologies available in the open source community
https://getfedora.org/en/server/prerelease/
- Get Fedora 23 Beta Cloud — build scale-out computing and utilize
the next generation of container deployment technology
https://getfedora.org/en/cloud/prerelease/
- Get Fedora 23 Beta Spins — alternative desktops for Fedora
https://spins.fedoraproject.org/prerelease
- Get Fedora 23 Beta Labs — curated bundles of purpose-driven
software and content
https://labs.fedoraproject.org/prerelease
What is the Beta release?
-------------------------
The Beta release contains all the exciting features of Fedora 23's
editions 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 23 is expected
in October.
We need your help to make Fedora 23 the best yet, so please take
some time to download and try out the Beta 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 rock-solid. 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.
Fedora-Wide Changes
-------------------
Fedora 23 includes a number of changes that will improve all of the
editions. For example, Fedora 23 makes use of compiler flags to
improve security by "hardening" the binaries against memory
corruption vulnerabilities, buffer overflows, and so on. This is a
"behind the scenes" change that most users won't notice through
normal use of a Fedora edition, but will help provide additional
system security.
Likewise, Fedora 23 has disabled SSL3 and RC4 by default due to
known vulnerabilities in the protocols. This means all applications
that use GNUTLS and OpenSSL libraries have had the SSL3 protocol
and RC4 cipher disabled.
Fedora 23 comes with the latest version of Mono 4. This means a big
improvement because we were stuck with an ancient version of Mono
(2.10) for too long. All packages within Fedora that are based on
Mono have been adjusted and rebuilt, to target the 4.5 version of
the .Net framework. Mono 4 does not support solutions targeting
v1.0, v2.0 or v3.5 of .Net, but usually they can be easily upgraded
to v4.5.
Fedora 23 Beta also includes support for Unicode 8.0, which
includes new emojis, and improvements in sorting Unicode text and
processing non-ASCII URLs.
Fedora Server
-------------
The Fedora Server release includes a number of interesting changes
and additions.
The rolekit service now supports setting up three roles. In
addition to the previously supported Domain Controller (powered by
FreeIPA abd Database Server (powered by PostgreSQL) roles, Fedora
Server 23 features a cache server for web applications (powered by
memcached).
Rolekit can also now be used from the anaconda kickstart by passing
the `--deferred` arguments to `rolectl`. For example: `rolectl
deploy domaincontroller --name=example.com --deferred` will
instruct the system to deploy the Domain Controller role on the
next boot.
The Cockpit Admin Interface in Fedora Server has several big
improvements as well.
- Support for SSH key authentication
- Support for configuring user accounts with their authorized keys.
- Basic cluster dashboard for driving Kubernetes on Fedora Server
and Fedora Atomic Host.
- Set the imezone for your Fedora Server from the Cockpit User
Interface (UI).
- Cockpit has also been made safe to use with multipath disks.
Fedora Workstation
------------------
While there's a lot going on under the hood, desktop users are also
going to find Fedora 23 Beta pretty exciting for all the obvious
goodness coming to the desktop. The easiest way to experience the
preview of these technologies is to download and try the Fedora 23
Beta Workstation edition.
Naturally, GNOME is getting an upgrade, with Fedora 23 containing a
preview of the upcoming GNOME 3.18 release, which is easier to use
than ever. There are also many enhancements on the way, such as:
- Improvements to next-generation graphics stack Wayland,
preparing it to be the default graphical server in a future release.
This includes mixed HiDPI support, to provide a better experience
when moving apps between HiDPI and non-HiDPI monitors
- Support for ambient backlight drivers, so brightness responds to
the environment on laptops with the required hardware
- The Software application is smarter about metered Internet
connections, and can now update system firmware
- Refreshed support for Google APIs to provide access to user data
through GNOME apps (including Google Drive integration)
Users trying to get a little work done on Fedora will be happy to see
LibreOffice 5 in Fedora 23. The new release includes a lot of new
features and improvements:
- Style previews in the sidebar
- Microsoft Word-compatible text highlighting
- Built-in image crop
- UI for data bars in Calc
- Support for Time-Stamp Protocol in PDF export
- Support for Adobe Swatch Exchange color palettes
- Import of Apple Pages files
- Improved support for HiDPI screens
- Significantly improved support for MS Office formats
Fedora Cloud
------------
Fedora 23 Cloud Base image includes many updates and enhancements to the
underlying Fedora base packages. For example, Fedora 23 now has the
latest Docker release, docker 1.8. We can now verify the publisher
of an image before running. This gives the users the power to identify
that the image publisher published has not been tampered with.
Stay tuned for news about Fedora Atomic Host in the not too distant
future!
Other notable changes in Fedora
-------------------------------
### Spins
Fedora Spins are alternative desktops for Fedora that provide a
different experience than the standard Fedora Workstation edition.
For instance, the Fedora KDE and Fedora Xfce spins provide popular
alternatives to GNOME for Fedora users who enjoy the KDE or Xfce
experience.
There's a new spin in town for Fedora 23. Want a classic take on a
modern desktop? If so, the Cinnamon spin may just be what you're
hoping to find. Fedora 23 includes a spin that tries to emulate the
GNOME 2 experience using GNOME Shell from GNOME 3.x.
Sugar on a Stick is a stand-alone implementation of the desktop
environment originally designed for the One Laptop per Child
project. Fedora's SoaS spin has been updated to Sugar 0.106, for
better performance, updated activities, and a new "social help"
feature for collaborative learning.
### Labs
Fedora Labs are curated software collections. You can find updated
live media focused on Games, Design, Robotics, and more.
Issues and Details
------------------
This is an Beta release. As such, 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 F23
Bugs page. https://fedoraproject.org/wiki/Common_F23_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
Release Schedule
----------------
The full release schedule planned is available on the Fedora wiki.
The current schedule calls for a beta release towards the end of
September, and the final release scheduled towards the end of October.
https://fedoraproject.org/wiki/Releases/23/Schedule
These dates are subject to change, pending any major bugs or issues
found during the development process.
I'm resending this announcement and FAQ from the bugzilla-announce list
as it will be of interest to Fedora Developers and users.
A Upgrade FAQ is available at:
https://bugzilla.redhat.com/docs/bugzilla-upgrade-faq.html
And the announcement post is:
https://www.redhat.com/archives/bugzilla-announce-list/2015-September/msg00…
(and copied below)
Dear Bugzilla User,
On September 20th we will upgrade the production Red Hat Bugzilla
servers as the next step in the ongoing Bugzilla Performance Improvement
Project.
To help users prepare for the production upgrade, we have upgraded
Partner Bugzilla, our public-facing staging system [1]. To ensure that
the changeover of the production system will be as smooth as possible,
we invite users to test their applications and RPC scripts against
Partner Bugzilla during the next two weeks and to submit any bug reports
via [2] no later than September 9th.
We expect that the production upgrade will provide a modest improvement
to overall performance and will enable us to make further improvements
in the future. The upgrade will also make Bugzilla more robust against
hardware failure.
In addition to upgrading the hardware, we will change the underlying
database from MySQL to PostgreSQL, which is better at handling
Bugzilla's database workload.
Neither upgrade should change the functionality offered by the Red Hat
Bugzilla user-interface or by the RPC APIs. If you observe any issues
that affect your applications or RPC scripts, please report them as soon
as possible.
Thank you,
-- The Red Hat Bugzilla Team
[1] https://partner-bugzilla.redhat.com/
[2] https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla
This Thursday, we will meet on irc.freenode.net in #fedora-meeting-2
to make sure we are coordinated and ready for the Beta release of
Fedora 23 on Tuesday, September 22, 2015.
Please note that this meeting will occur even if the release is
delayed at the Go/No-Go meeting on the same day two hours earlier.
Please follow the [FedoCal] link to find the time of the meeting in
your time-zone.
[FedoCal] https://apps.fedoraproject.org/calendar/Fedora%20release/#m2676
You may received this message several times as this meeting is opened
to all teams. I also hope this will raise awareness and more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
Thanks for attending,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 23
Beta.
Please follow the [FedoCal] link to find the time of the meeting in
your time-zone.
[FedoCal] https://apps.fedoraproject.org/calendar/Fedora%20release/#m2677
"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:
https://fedoraproject.org/wiki/Go_No_Go_Meeting
In the meantime, keep an eye on the Fedora 23 Beta Blocker list:
http://qa.fedoraproject.org/blockerbugs/milestone/23/beta/buglist
Thanks for attending,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Dear Red Hatters,
I am happy to announce the Call For Participation for DevConf.cz 2016. This is the 8th DevConf.cz, a free annual conference for all Linux and JBoss Community Developers, Admins and Linux users organized by Red Hat Czech Republic in cooperation with the Fedora and JBoss communities.
The deadline for submitting your talk and/or workshop proposal is November 30th 2015! As always we're looking for technical topics, developer oriented, new technologies, new tools, cool things and great hacks! Submit your talk or workshop idea now [0]!
The event takes place during the first weekend of February 2016 (5-7 February) in Brno, Czech Republic.
For more information please visit the official website [1], follow us on social networks [2,3,4], or feel free to contact me.
[0] www.devconf.cz/cfp
[1] www.devconf.cz
[2] https://plus.google.com/events/cdh2uqg6afthljoqviec23tvt0k
[3] @devconf_cz
[4] facebook.com/DevConf.cz
Best Regards
Jan Bleha ■ Community coordinator ■ Red Hat Czech s.r.o.
Mob.: +420 702 153 774 ■ Tel.: +420 532 294 537
Purkyňova 99/71 ■ 612 45 Brno ■ Czech Republic
IC: 27690016 ■ www.cz.redhat.com
Hi all,
Tuesday was an important day on the Fedora 23 schedule[1], with two
significant cut-offs.
Tuesday was the Beta freeze[2]. This means that only packages which
fix accepted blocker or freeze exception bugs[3][4] will be marked as
'stable' and included in the Beta composes. Other builds will remain
in updates-testing until the Beta release is approved, at which point
the Beta freeze is lifted and packages can move to 'stable' as usual
until the Final freeze.
Finally, Tuesday was the '100% code complete deadline' Change Checkpoint[8],
meaning that Fedora 23 Changes must now be ' New accepted changes must be code
complete, meaning all the code required to enable to the new change is
finished. The level of code completeness is reflected as tracker bug state
ON_QA. The change does not have to be fully tested by this deadline'.
Regards
Dennis
[1] https://fedoraproject.org/wiki/Releases/23/Schedule
[2] https://fedoraproject.org/wiki/Milestone_freezes
[5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[8] https://fedoraproject.org/wiki/Changes/Policy
= Proposed Self Contained Change: Anaconda Using LVM DBus API =
https://fedoraproject.org/wiki/Changes/Anaconda_Using_LVM_DBus_API
Change owner(s):
* Vratislav Podzimek <vpodzime AT redhat DOT com>
* Jonathan Brassow <jbrassow AT redhat DOT com >
A new DBus API for LVM is being created so let's make the installation
process use it for setting up LVM storage.
== Detailed Description ==
For quite a long time there has been a request for a better API for
LVM than what the current CLI tools provide. After a quite long
discussion between the interested groups it has been decided that a
DBus API should be the best choice. The LVM team has thus been working
on a prototype implementation of such DBus API, but we ended up in a
circle between "there's not enough time spent on the LVM DBus API
because nobody's using it and thus it's not high priority" and
"nobody's using the LVM DBus API because there's not enough time spent
on it". To break this circle and get from the deadlock, we would like
to make the installation process use the LVM DBus API and thus pioneer
its usage for others and make sure it is maintained, improved and
considered a high-enough priority by the LVM team due to a real usage
in an important component of the system/distribution. The reasons for
why the installation process could be the first one to use the new API
are the following facts:
* anaconda+blivet are written in Python so the performance of the LVM
DBus daemon prototype also written in Python shouldn't be an issue
* anaconda+blivet only do basic operations with LVM in the
installation process so we could start with this limitted scope
* blivet uses libblockdev as its backend and libblockdev is modular
having the LVM functionality as a plugin which can be replaced with a
new plugin using the DBus API where possible while keeping the
old/current plugin as a backup solution if it turns out the LVM DBus
API is * not production ready even for the installation use case. This
results in a wonderful Contingency plan (see below).
== Scope ==
* Proposal owners: implement the LVMDBus libblockdev plugin
(vpodzime), make sure the LVM DBus daemon is packaged for Fedora and
production ready for the installation use case (jbrassow)
* 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)
* 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