At the Fedora 20 Beta Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 20 Beta by Fedora QA and Fedora
Development (with silent approval from me ;-).
Fedora 20 Beta will be publicly available on Tuesday, November 12,
Due to possible collision with holidays, FESCo approved  one
week shorter Beta to Final period with Final Change Deadline on
Nov 26. Be aware of this change and queue your updates on time!
Many thanks to everyone who helped with this release and fixing
Meeting details can be seen here:
= Proposed Self Contained Change: OpenCL =
Change Owner(s): Fabian Deutsch <fabiand(a)fedoraproject.org>
This change will bring basic OpenCL support to Fedora to support the
development of OpenCL enabled software and the development of OpenCL
implementations itself. The change includes enabling Mesa's OpenCL state-
tracker (in 9.3 with ICD support), packaging pocl - an CPU only OpenCL
implementation - and the introduction of several other OpenCL related
== Detailed description ==
The change is intended to give developers a starting point to be able to use
OpenCL and to improve existing OpenCL implementations.
The change will include the following sub changes:
Add OpenCL implementations
* Enable OpenCL state-tracker in Mesa NEW
* Package pocl - CPU-only OpenCL implementation DONE
* Package beignet - Intel Ivy Bridge 1 only
Package implementation dependencies:
* Package libclc - needed by Mesa's state-tracker DONE
* Fix OpenCL path owenrship - Who owns /etc/OpenCL DONE
* Review Request: opencl-filesystem - OpenCL filesystem layout - A package
owning shared paths DONE
Package related packages
* Review Request: gocl - GLib/GObject based library for OpenCL - glib based
OpenCL library DONE
* Review Request: clinfo - Enumerate OpenCL platforms and devices - A tool to
query informations about the available OpenCL platforms DONE
* Review Request: erlang-cl - OpenCL binding for Erlang DONE
* Package ViennaCL - A math library whcih can utilize CPU (OpenMP) and GPU
* Package pyopencl - A python library for accessing OpenCL BLOCKED BY rhbz
* Package ocltoys - A couple of OpenCL examples for testing NEW
* Update existing packages if needed
** gegl (to be investigated)
** ocl-icd (done)
* Potential projects to be packaged:
** Package khronos icd - probably not
** Package radeontop - To monitor a Radeon GPU (which supports OpenCL)
** Package piglit - This will be a testuite for the OpenCL implementations,
has some non-fedora deps
* Other stuff:
** Add a new group to comps or a opencl-dev package?
** Add virtual provides to the opencl implementations - So a app requiring
opencl just needs to require the virtual package (so any provider)
** Version opencl-headers
== Scope ==
Proposal owners: Mainly packaging
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)
= Proposed System Wide Change: Python 3.4 =
Change owner(s): Slavek Kabrda <bkabrda(a)redhat.com>
Update the Python 3 stack in Fedora from Python 3.3 to Python 3.4.
== Detailed description ==
Python 3.4 adds numerous features and optimizations. See the upstream notes at
== Scope ==
Compare with the Python 3.3 feature page .
We need to wait for Python 3.4 to reach feature freeze (planned for 3.4.0 beta
1: November 24, 2013), so that the bytecode format for .pyc files is frozen,
together with the ABI for extension modules.
At that point we can rebase python3 to the latest release candidate of that
code. We would then need to rebuild all python 3 packages. See
For bonus points, we ought to tell "file" and "rpmlint" about the new bytecode
format for .pyc files.
Note that the suffix of some files should change, and this may require slight
packaging tweaks in the various packages that ship Python 3 code:
* bytecode files changing from .cpython-33.pyc (and .cpython-33.pyo) to
.cpython-34.pyc (and .cpython-34.pyo)
* extension modules changing from .cpython-33m.so to .cpython-34m.so and
.cpython-33dm.so to .cpython-34dm.so
Notes about porting from Python 3.3 can be found at
Proposal owners: This change is isolated to Python 3 stack, which is not yet
crucial for Fedora. Still, as the time of moving Fedora to Python 3 is
hopefully approaching, we need to do this very cautiously. I will prepare
Python 3.4 prerelease RPMs in a private repo and will do a test rebuild of all
Python 3 dependent packages, filing bugs/sending patches to upstreams. This
will give us a good notion of how drastic this change will be and whether or
not we really want to undergo it. Overall, the change should have roughly this
* After change is accepted: Start building Python 3.4 prereleases in a private
repo, continuously upgrading with latest upstream prerelease versions.
* November 24, 2013 (3.4.0 beta 1: feature freeze): Start rebuilding Python 3
dependent packages in the repo.
* February 23, 2014 (3.4.0 final) If everything goes well (meaning that all
essential packages in Fedora build and work with Python 3.4) up to this point,
merge into F21.
Other developers: I'll gladly accept any help with
rebuilding/porting/patching/bug reporting of dependent packages as well as
suggestions for Python 3.4 packaging itself. When we're sure that we really
want to do the transition, it'd be great if package owners rebuilt their
Release engineering: Nothing.
Policies and guidelines: None.