The first Fedora 14 Alpha Go/No-Go Meeting was held 2010-08-12 at 12:00
UTC (so evening of 2010-08-11 in North America). The outcome of the
meeting was a decision to slip the Alpha release by one week due to one
bug agreed to be a definite blocker:
https://bugzilla.redhat.com/show_bug.cgi?id=623129 "xdriver=vesa is not
and one bug that is potentially a blocker, pending more data:
https://bugzilla.redhat.com/show_bug.cgi?id=596985 "hang at start of X11
on fresh install from DVD"
All other bugs considered were agreed not to be release blockers and
removed from the list.
A slip announcement will be sent with more details on the slip
specifically. We aim to build an RC4 tomorrow afternoon American time
(2010-08-12) with the fix for 623129 (and possibly fixes for a couple of
other bugs we decided were not blockers but would be nice to fix), and
continue to research 596985 to decide if it is a blocker. If we decide
it is, an RC5 build will be required.
The automated summary of the meeting can be found here:
The full log of the meeting can be found here:
Thanks to all for attending and providing input.
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
Today we held our readiness meeting for the Alpha release of Fedora
14. As you may know, this is a meeting with representatives from the
Development, Release Engineering, and Quality Assurance teams. In
these meetings, we evaluate the list of blocker bugs and give a "go"
or "no go" signal on the state of the Fedora release.
You can read the minutes of the meeting here, but in short the
decision was made that the release has not passed its release
criteria. When this happens, the entire release schedule is
slipped by a week, and we work to get things in better shape for the
next meeting. We'll get the schedule updated in the next day or
so, but in general this means that our general availability date for
Fedora 14 has now gone from October 26th to November 2nd.
During composition of any further release candidates, the Fedora
Release Engineering and Quality Assurance teams plan to be quite
conservative in the updates they pull into the release candidates, so
that we don't inadvertently create more blocker bugs. I'd also like to
thank those who have really pushed hard to try to get the Alpha into
shape. In particular, the Release Engineering team put in a lot of
extra hours to compose our release candidates, and the QA team did a
fantastic job of testing the release candidates and knocking out as
many blocker bugs as possible.
While I regret the fact that the schedule has slipped, I'm confident
it was the right decision to ensure that Fedora 14 is a rock-solid
Fedora Project Leader
a lot of packages were rebuilt for Python 2.7 recently, but
unfortunately they've turned out to be not all that needed rebuilding.
Essentially, all packages that contain .py files that aren't
below /usr/lib(64)/python need to be rebuilt so that their respective
pre-built .pyc/.pyo files are built with the new Python version.
If the packages aren't rebuilt, python will either attempt to rebuild
the .pyc/.pyo files (and fail due to SELinux policy) during runtime (if
run as root) or the program will take longer to startup because the
python interpreter needs to parse the .py files everytime (and can't
just use the respective .pyc/.pyo files since they're invalid).
The reason why this hasn't been noticed/why those packages haven't been
covered in the mass rebuild is because they don't require
"python(abi)" (which was used to find out which packages to rebuild)
even though the contained .pyc/.pyo files clearly do. This is because
the pythondeps.sh used by rpmbuild only adds that dependency to packages
which have modules in the standard paths.
Thanks to Kalev Lember who wrote a script identifying the affected
packages. Using its output, Dave Malcolm has just mass-filed bugs
against the packages which we could identify and he's looking to get
these rebuilt en-masse as well. Owners or comaintainers still would need
to file update requests so the packages actually end up where the users
can get them ;-). For this purpose, I've attached two lists to this
mail: one listing the affected packages and their owners and
comaintainers, the other listing the affected packages each person owns
Please file updates when your packages have been rebuilt and nag us if
they don't get rebuilt in time, whatever that means.
Thanks for your help,
: https://bugzilla.redhat.com/show_bug.cgi?id=621726 - 'SELinux is
preventing /usr/bin/python "write" access
: https://bugzilla.redhat.com/show_bug.cgi?id=623233 - 'python(abi)
autodetection needed for all .py[co] files, not just those
Nils Philippsen "Those who would give up Essential Liberty to purchase
Red Hat a little Temporary Safety, deserve neither Liberty
nils(a)redhat.com nor Safety." -- Benjamin Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
Sending on behalf of Dave Lawrence. This will affect Fedora too.
REMINDER: Red Hat Bugzilla (bugzilla.redhat.com) will be unavailable on
August 13th starting at 9:00 p.m. EDT [01:00 UTC] to perform
an upgrade from Bugzilla 3.4 to Bugzilla 3.6. We are hoping to be
complete in no more than 5 hours barring any problems. Any
services relying on bugzilla.redhat.com may not work properly during
this time. Please be aware in case you need use of those
services during the outage.
Also *PLEASE* make sure any scripts or other external applications that
rely on bugzilla.redhat.com are tested against our test
server before the upgrade if you have not done so already (see original
email below). Let the Bugzilla Team know immediately of any
issues found by reporting the bug in bugzilla.redhat.com against the
Bugzilla product, version 3.6.
The Red Hat Bugzilla team is happy to announce another public beta
release of the next version of Red Hat Bugzilla based on the
upstream 3.6 code base.
Please test drive at:
Over the years Red Hat has made substantial customizations to Bugzilla
to fit into the Engineering
tool chain. Over time the upstream has incorporated some of these
customizations or solved them in different ways. Upgrading reduces
our customization footprint (and thus maintenance) while bringing many
bug fixes & enhancements.
The main area of focus for our public betas is stability. Functionality
that currently works in our 3.4 code base should continue to
work as expected in the new 3.6 release. These include various ajax
optimizations, needinfo actor support, frontpage.cgi, product
browser, several various UI enhancements, and of course the XMLRPC API.
Please feel free to point your various scripts and third party
applications that use the XMLRPC API at the test server to make sure
they continue to function properly.
There are numerous other changes behind the scenes that we haven't
listed. The goal is to make sure that functionality that people
have come to expect in 3.4 is possible in the new system.
There are also numerous new features/fixes that are part of the upstream
3.6 release. For more detailed information on what has
changed since the last release, check out the release notes page at
The database is a recent snapshot of the live database so should be
useful for testing to make sure the information is displayed
properly and changeable. Also with a full snapshot it is possible to
test for any performance related issues. Email has been
disabled so that unnecessary spam is not sent out. So
feel free to make changes to bugs to verify proper working order.
We are asking for everyone to get involved as much as possible with
testing and feedback on the beta releases to help us make this
the most robust and stable release possible.
Please file any enhancement requests or bug reports in our current
Bugzilla system at https://bugzilla.redhat.com . File them under
the Bugzilla product and relevant component with the version 3.6. With
everyone's help we can make this a great release.
The Red Hat Bugzilla Team
It's been an exciting ride so far and we're embracing the peaks and
valleys of the Fedora release process in real time. Even with all the
recent changes and bugs we still have a shot at creating the Fedora 14
Release Candidate on schedule TOMORROW. Failure to successfully build
the RC tomorrow could put the Fedora 14 Alpha at risk and push out the
rest the schedule.
In order for Release Engineering to create the Fedora 14 Alpha RC, all
of the bugs below must be in a state of CLOSED or ON_QA by
tomorrow--Bodhi updates have been submitted and the packages are in
updates-testing. And, no new blocker bugs are identified before then.
If there are other bugs that are of concern that you believe meet the
release criteria, add 'f14alpha' as a blocker or ask for help on #fedora-qa.
Thank you package maintainers and testers for all that you do!
597858 :: NEW :: xdg-utils :: Rex Dieter :: "SELinux is preventing
firefox from making its memory writable and executable." crashes rawhide
firefox start :: https://bugzilla.redhat.com/show_bug.cgi?id=597858
--waiting to confirm availability of new selinux-policy
620623 :: ASSIGNED :: distribution :: Bill Nottingham :: Packages with
unresolved dependencies ::
--need rebuilt dependencies:
--need rebuilt dependencies:
620949 :: ASSIGNED :: gnome-panel :: Ray Strode [halfline] :: [abrt]
gnome-panel-2.31.4-3.fc14: Process /usr/bin/gnome-panel was killed by
signal 11 (SIGSEGV) :: https://bugzilla.redhat.com/show_bug.cgi?id=620949
--waiting for new build and submission to Bodhi
619889 :: ASSIGNED :: xorg-x11 :: X/OpenGL Maintenance List :: X.org
pegged at 100% CPU usage after booting with systemd ::
--waiting for new build and submission to Bodhi
615443 :: MODIFIED :: livecd-tools :: Bruno Wolff III :: booting live
images from nightly fails (can't mount root filesystem) ::
--appears to be fixed? Has packaged moved to updates-testing?
620900 :: MODIFIED :: anaconda :: Anaconda Maintenance Team :: traceback
on install of F14 Alpha Test Compose #2 ::
--should be fixed, need a new compose
617115 :: ON_QA :: livecd-tools :: Bruno Wolff III :: rawhide live spins
showing black screen instead of syslinux boot menu ::
--Needs Bodhi feedback
Dear package maintainers
This is kind reminder that it is F14 Software String Freeze today 03-Aug.
Please update your POT with latest strings. All translators will be
working hard to update your package translation.
To ensure high quality translations in the final release, please be
aware Software String Freeze Policy . If you think that you need to
break the string freeze, then please ask for approval from the Fedora
Localization Team prior to breaking the freeze .