Fedora 19 Go/No-Go Meeting, Thursday, June 27 @ 17:00 UTC
by Jaroslav Reznik
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 19.
Thursday, June 27, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"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 19 Blocker list:
http://qa.fedoraproject.org/blockerbugs/milestone/19/final/buglist
There are currently three unresolved accepted blockers, for full
status see mail [1] by adamw. Please help with the release of
Fedora 19, take a look on bugs assigned to you!
Reminder: the Readiness meeting follows up the Go/No-Go meeting two
hours later.
[1] https://lists.fedoraproject.org/pipermail/devel/2013-June/184345.html
Jaroslav
10 years, 10 months
poppler soname bump in rawhide
by Marek Kasik
Hi,
I plan to rebase poppler in rawhide to poppler-0.22.4 at the beginning
of the next week (24th of June).
There are several changes (new parameters of some functions and new
private members of some classes (Stream, Gfx, DCTStream and TextWord))
and 1 soname bump (libpoppler.so.34 to libpoppler.so.37).
Regards
Marek
10 years, 10 months
F20 System Wide Change: python-setuptools update to 0.7.x
by Jaroslav Reznik
= Proposed System Wide Change: python-setuptools update to 0.7.x =
https://fedoraproject.org/wiki/Changes/Python_setuptools_0.7
Change owner(s): Toshio Kuratomi <toshio(a)fedoraproject.org> with help from
Bohuslav Kabrda, Nick Coghlin, and the Python SIG
Update to a new upstream release of python-setuptools that is not completely
compatible with previous releases.
== Detailed description ==
python-setuptools is used as a buildtime dependency in many packages. It is
also a runtime dependency for some packages where it provides a way to load
plugins, load data files, and specify what versions of dependent packages are
needed. In Fedora, we also make use of its multiversioning features to install
some backwards compatibility packages.
The upstream for the python setuptools package has been in a maintenance mode
for many years. During that time we have been shipping a fork, python-
distribute, which has added bugfixes and python3 compatibility but not
significantly altered the API. Just recently, python-setuptools upstream has
become active and released a new version that merges the two forks and is not
completely API compatible. As the older versions won't see bug fixes anymore,
we need to move to this new version but there could be some usages that are
broken by the new version.
10 years, 10 months
F20 System Wide Change: Perl 5.18
by Jaroslav Reznik
= Proposed System Wide Change: Perl 5.18 =
https://fedoraproject.org/wiki/Changes/perl5.18
Change owner(s): Petr Písař <ppisar(a)redhat.com>, Jitka Plesníková
<jplesnik(a)redhat.com>
A new perl 5.18 version brings a lot of changes done over a year of
development. See [1] for more details.
== Detailed description ==
New perl is released every year and updates containing mainly bug fixes follow
during the year. The 5.18.0 version is stable release this year and 5.18.1 and
subsequent revisions will follow during the year to fix issues introduced in
5.18.0.
Because of change in dlopen(3) from RTLD_GLOBAL to RTLD_LOCAL (bug #960048)
[2], we will try to link all native perl module DSOs to libperl.so explicitly.
This item needs discussion. Current status does not allow to use perl
interpreter via dlopen() from other programs (like slapd, snmpd), but proposed
change can bring other unforeseen difficulties (like double-linking).
[1] http://search.cpan.org/dist/perl-5.18.0/pod/perldelta.pod
[2] https://bugzilla.redhat.com/show_bug.cgi?id=960048
10 years, 10 months
Flock proposals now open for community voting
by Tom Callaway
Thanks to the Fedora Community for submitting 125 awesome talks,
hackfests, sprints and workshops for Flock, our new contributor conference!
We've taken those submissions and put them in the Fedora Elections web
application, and now, it is time for you to give us your feedback. These
proposals have been submitted by the Fedora community and we want the
Fedora community to tell us what _you_ want to see! Even if you cannot
attend Flock in person, these sessions will be streamed and recorded, so
your vote is appreciated!
If you have a Fedora Account (they are free to create), and have agreed
to the Fedora Project Contributor Agreement (FPCA), you can vote for the
125 submissions here:
https://admin.fedoraproject.org/voting/vote/flock-2013
Need a Fedora Account? Go to:
https://admin.fedoraproject.org/accounts
Want to know more about Flock? Go to:
http://flocktofedora.org
The way that the voting works is this:
For each submission, you can give it any score between 0 ("do not want")
and 125 ("WANT WANT WANT WANT WANT!!!!"). Next to every submission title
is a link to the abstract for the submission, which usually (though not
always) contains a longer explanation. These submissions are mostly
anonymized (some people put their names or enough details in the
abstracts to make it obvious who the proposed speakers were). This is
intentional, as we are trying to eliminate an area of potential bias. We
want the ideas behind these submissions to be the area of focus, and not
be overly biased by the speaker.
Voting is now open, and will remain open until 2013-06-10 04:00:00 UTC
(12:00 AM Eastern Time).
Please note: While the voting results will weigh heavily upon the final
Flock schedule, they will not be used as the sole determination for
accepted talks.
On behalf of everyone working on Flock, thanks,
Tom Callaway
==
Fedora Project
10 years, 10 months
Fedora 20 new planning process and schedules
by Jaroslav Reznik
Hi!
Fedora 19 is close (let's hope it's alive) to the release and it's
again the time to start planning for the upcoming version.
For Fedora 20, in coordination with FESCo [1], the new Planning process
was developed to replace the old, not satisfactory Feature process.
In reality, it's pretty similar to the exercise we did for the
Fedora 19 - with announcements, less burden for FESCo (and now also
developers) for leaf, self contained changes and more time to
coordinate system wide changes with impact to the rest of distribution
and schedule. To emphasize the aim on the cross team/distribution
coordination (development, documentation and marketing), Features are
now called Changes.
For the full description, policies and how-tos (to submit a proposal),
see [2]. The new empty template is now available too, with detailed
instructions how to fill it in.
Again as we did for Fedora 19, final Fedora 20 schedule [3] will be
based on the scope of submitted Change proposals. In the schedule,
all milestones after the submission deadline are marked as "no earlier
than" and we are not committed to make these dates! But this gives
more information for non-development teams to plan Fedora 20 tasks.
===== IMPORTANT! =====
Change Proposals Submission Deadline is set to 2013-07-16.
======================
Don't hesitate to ask any question or we'll be more than happy to
see more suggestions etc. For docs/marketing coordination more info
will come via appropriate channels.
PS1: Please, review your old Features that are in the Ready for Wrangler
category (mostly as result of postponing F19 ones to F20) if you still
plan to deliver them and let me know. I'll help you with transition
to the new Change Proposal template.
PS2: Flock talk/workshops are proposed for the new planning process,
so we can follow up the FUDCon Lawrence discussion and also it
will be right after Change freeze and I hope we will have more
feedback and experiences with changes we made. Blog post with more
details will follow soon.
Jaroslav
[1] https://fedorahosted.org/fesco/ticket/896
[2] https://fedoraproject.org/wiki/Changes/Policy
[3] https://fedoraproject.org/wiki/Releases/20/Schedule
10 years, 10 months
