There's a new devel release of the above just landed. I'll be looking
to get them into rawhide over the new couple of days but there's been
quite some change so I'm going to deal with it all locally first to
see what the impact is before I push it.
= Proposed System Wide Change: Java 8 =
Change owner(s): Omair Majid <omajid(a)redhat.com>
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.
== Detailed Description ==
The current default Java 7 runtime in Fedora is OpenJDK 7. The latest version
of OpenJDK, 8, was released on 18 March 2014. Given that Fedora 21 will not be
released before August, it makes sense to include the latest version of
OpenJDK in Fedora 21.
OpenJDK 8 is a significant update to Java. It brings in significant new features
new library features. A complete list of features is available .
OpenJDK 8 is a backwards compatible update. Theoretically everything that
worked against OpenJDK 7 should continue working against OpenJDK 8. There are
a few exceptions:
OpenJDK8 is much more strict when it comes to building javadocs. Many -
javadoc package in Fedora fail to build. Those that are built should continue
working just fine.
Packages that rely on non-public OpenJDK API may fail to build/run.
A complete list of incompatibilities is available . The incompatibilities
are source and behavioral only.
It may be a good idea to mass rebuild Java packages against OpenJDK 8 to spot
any source incompatibilities earlier. This is not required.
== Scope ==
* Proposal owners:
** Deprecate/Obsolete java-1.7.0-openjdk
** Promote java-1.8.0-openjdk to a full java runtime status (fix provides in
** In case of a mass rebuild, supply/apply patches to fix build against OpenJDK
* Other developers:
** icedtea-web maintainers will need to update icedtea-web to run against
** Other java packagers will need to apply patches to their java package to
ensure they can build against OpenJDK 8
** Everyone will need to test packages to verify that they work against
* Release engineering:
** Remove java-1.7.0-openjdk
** Possibly mass-rebuild (?) all Java packages. This is not strictly required
to make OpenJDK 8 the default Java runtime.
* Policies and guidelines:
** Many -javadoc packages fail to build. The OpenJDK 8 maintainers and the
Java SIG are working on identifying a solution. The solution may require 
guideline changes making -javadoc subpackages optional.
devel-announce mailing list
We'd like to update to Mesa 10.1 in Fedora 20, since the cycle is so
long before F21 and (among other goodies) it enables OpenGL 3.3 on some
newer Radeons. This implies rebasing LLVM 3.4, and that's where it gets
a little awkward: the OpenGTL package only works up to LLVM 3.3.
However, OpenGTL is dead upstream, and the only thing requiring it in
F20 gold - calligra-krita, by way of libQtGTL - has already been updated
to Obsolete OpenGTL. As far as I know OpenGTL is the only such package
we have requiring LLVM 3.3, so the rest of the rebase should just be a
matter of updating to match F21.
The following source packages will also be updated for the llvm rebase:
If there are no serious objections I'll try to get this all into testing
early next week. If you _do_ happen to be using OpenGTL for something
in F20, now would be an excellent time for you to start working on
porting it to current LLVM.
I am looking for someone to walk me through the Anaconda source as I need
to understand it and cannot find where its 'main' is and how it launches X
Windows as I need to work out why the main installer is not working on my
HP D140 G3's with MCA video controllers.
Hope someone kind person has time to help me.
WG meeting will be at 12:00 UTC, 14:00 Central Europe, 8:00 Boston, 5:00
San Francisco, 21:00 Tokyo in #fedora-meeting on Freenode.
I hope time make sense. Otherwise please comment the thread about
== Topic ==
* Automatically approve topics, which weren't refused on mailing list:
* Open Questions - Playground: Signing
* Open Questions - Playground: Provenpackagers
* Approve on list or irc:
* Open Questions - distinguish packages
* Does my proposal passed or not?
* Proposal: Do not try to distinguish them. Rpmfusion packages also
don't have different dist tag. You can find out if really want to by rpm
-something or check key, which will be also different.
* Open Questions - Playground: reviews
* Are conflicts inside Playground repository allowed?
* How many other checks do we want to have?
* 1 Big repo vs multiple small ones - finally decide which one to pick
* finish change proposal
= Proposed Self Contained Change: NFS Ganesha File Server =
Change owner(s): Jim Lieb <lieb(a)sea-troll.net>
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
== Detailed Description ==
NFS Ganesha is a user-mode file server for NFS (v3, v4.0 , v4.1 pNFS) and for
9P from the Plan9 UNIX O/S. It integrates with backend filesystems via its File
System Abstraction Layer (FSAL) which is a set of loadable modules that
implement the access to these filesystems. Using a FSAL is similar to FUSE in
that the whole filesystem can be implemented in user space. This is especially
advantagious for pNFS and distributed filesystems where storage is distributed
across a network. For backend (FSAL) modules than can be supported , see
Those FSALs labeled as Yes are packaged for Fedora. Those labeled Not Yet
require upstream packages that are not available yet. Those labeled No cannot
be packaged with Fedore either due to licensing or availability.
NFS Ganesha supports pNFS as both a metadata server (MDS) and a data server
(DS). It supports both files and object layouts for depending on what is
supported by the underlying filesystem.
== Scope ==
This is a new package based on the new V2.0.0 upstream release. No other
changes to the system are required.
* Proposal owners: The upstream just released (DEC 2013) V2.0.0. Initial
packaging is complete and accepted. The package will be updated during the
development period to the latest stable release.
* 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)
devel-announce mailing list
I promised a while ago that I would provide a text version of my talk at
DevConf, for people who couldn't make it and because sitting through a video
of me standing up there going on and on doesn't really make for good
I posted a link to the first part last week:
and now, Part II:
And as I said last week, I will take questions, comments, complaints, in any
media including replies here, on the article, on the social media, or at any
bar or coffee shop within walking distance of Boston's MBTA.
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
"Tepid change for the somewhat better!"