Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2013-05-30 16:00 UTC in #fedora-meeting-1 on
Local time information (via. rktime):
2013-05-30 09:00 Thu US/Pacific
2013-05-30 12:00 Thu US/Eastern
2013-05-30 16:00 Thu UTC <-
2013-05-30 17:00 Thu Europe/London
2013-05-30 18:00 Thu Europe/Paris
2013-05-30 18:00 Thu Europe/Berlin
2013-05-30 21:30 Thu Asia/Calcutta
2013-05-31 00:00 Fri Asia/Singapore
2013-05-31 00:00 Fri Asia/Hong_Kong
2013-05-31 01:00 Fri Asia/Tokyo
2013-05-31 02:00 Fri Australia/Brisbane
Links to all tickets below can be found at:
= Followups =
#topic #276 Bundling libxdiff in libgit2
= New business =
#topic #295 Add note about network access to guidelines
#topic #296 Simplifying Ruby Packaging Guidelines
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
Good day all,
Please join us today (Wednesday, May 29th) at 4PM EDT (8PM UTC)
for the Fedora ARM weekly status meeting in #fedora-meeting-1 on Freenode.
On the agenda so far..
0) Status of ACTION items from our previous meeting
1) Problem packages
2) Kernel Status Update
3) Aarch64 Status Update, problem packages
4) Blockers for F19 GA
5) Flock Planning
6) Open Floor
If there is something that you would like to discuss that isn't mentioned
please feel free to bring it up at the end of the meeting or send an email
to the list.
in upstream GNOME, we're starting to convert the 'make check' style
tests in many modules into installed tests that can be run against an
installed system. We run these tests in our build system whenever a
build completes. You can see this in action here:
http://build.gnome.org/#gnome-ostree (the Integrationtest line).
I think these tests can be useful for Fedora qa as well, which is why I
am mentioning this here. I've just built the first glib2 release with
installed tests in rawhide. For now, I've put the tests in a glib2-tests
subpackage. The package contains the test binaries
(in /usr/libexec/glib/installed-tests) and metadata describing the tests
I expect that we'll see some more GNOME packages grow -tests subpackages
over the next months (gtk, gjs, libsoup, ...)
To run the tests upstream, we use a simple test runner called
gnome-desktop-testing-runner, which we could package as well. But the
metadata is very simple keyfiles, so it should be easy to adapt some
other test harness to use them, if desired.
All of this is still up for discussion, and we can make changes to make
the tests useful downstream as well as upstream.
Let me know what you think.
Hey, folks. Just a heads-up: in recent releases the anaconda team have
started a policy of more or less 'freezing' anaconda for the whole
post-Beta period. Apart from some specific planned developments, they
intend to mostly take only fixes for Freeze Exception and Blocker bugs
into anaconda between Beta and Final, starting right now (not starting
from the official, project-wide freeze on June 16).
So please, when testing and filing bugs, nominate bugs that you believe
should be fixed in Fedora 19 Final as 'freeze exception' bugs. You can
do this easily by using the blocker/FE nomination web page:
or of course you can use the 'old-skool' process, which is just to mark
the bug as blocking 'FinalFreezeException'.
To avoid the load getting too large, if your bug is not of very critical
impact, it might be best to nominate it only if you know the devs are
actively working on a fix; it'd be a waste of people's time to review a
bunch of bugs that the devs didn't have time to work on. If your bug
seems pretty important, go ahead and nominate it straight away, as we'll
probably want to have it on the radar.
We were already planning to start doing blocker review meetings
tomorrow, so we'll make sure to review proposed anaconda freeze
exception bugs during review meetings from now on, and thereby make sure
the appropriate fixes are 'approved' to go into f19 final.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
The Fedora ARM team is pleased to announce the Fedora 19 Beta for ARM is now
available for download from:
This marks the last significant milestone before reaching the final release of
Fedora 19 for ARM, with only critical bug fixes being added as updates to make this
our most solid release to date.
This marks the first time the Fedora ARM team will be releasing the F19 Beta
alongside Primary Architectures.
The Fedora 19 Beta for ARM includes two pre-built images - one for use with the
Pandaboard and Pandaboard ES which require special partitioning, the second will
support the Trimslice and Versatile Express(QEMU). The Beta for ARM also includes an
installation tree in the yum repository which may be used to PXE-boot a
kickstart-based installation on systems that support this option, such as the
Calxeda EnergyCore (HighBank).
For additional information including detailed installation instructions, please visit
the Fedora 19 Beta for ARM page:
Join us on the IRC in #fedora-arm on Freenode or send feedback and comments to the
ARM mailing list.
On behalf of the Fedora ARM team,