Hey, folks. It's that time again - time to start thinking about Test
Days for Fedora 18.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization, or any combination of the
two. To propose a Test Day, just file a ticket in QA trac - full details
are at https://fedoraproject.org/wiki/QA/Test_Days/Create . For
instructions on hosting a Test Day, see
You can see the schedule at
https://fedoraproject.org/wiki/QA/Fedora_18_test_days . There are many
slots open right now, with the earliest on 2012-08-09 and the latest
2012-11-01. Consider the development schedule, though, in deciding when
you want to run your Test Day - for some topics you may want to avoid
the time before the Alpha release or the time after the feature freeze
or the Final freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific timeframe due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or timeframe you'd
like, and we'll figure it out from there.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any other member of the QA team on test@ or in
#fedora-qa on IRC. Thanks!
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
FESCo on 2012-11-28 meeting agreed to initially target an end-of-May
release with an end-of-February branch date, but may adjust outwards
depending on submitted features .
The Feature Submission Deadline is now set to 2013-01-29 and the F19
submission period window is open .
Schedule will be made at or shortly after the Feature Submission
Deadline based on the review of submitted features and will be
announced per usual means . To make the planning easier, please
make sure to submit feature proposals with well defined scope.
FESCo also agreed on additional Wednesday and Thursday release days
but Tuesday is still the preferred target release day  - applies
to Fedora 18 either.
The Fedora 18 "Spherical Cow" Beta release is rolling! This release offers a
preview of some of the best free and open source technology currently under
We are delighted to announce the availability of the beta release of Fedora
18. Want to get a taste of the future? Download it now:
*** What is the Beta Release? ***
The Beta release is the last important milestone of Fedora 18. Only critical
bug fixes will be pushed as updates leading to the general release of Fedora 18
in the beginning of the next year. We invite you to join us in making Fedora
18 a solid release by downloading, testing, and providing your valuable
Of course, this is a beta release, meaning that some problems may still be
lurking. A list of the problems we already know about is found at the Common
F18 bugs page, seen here: http://fedoraproject.org/wiki/Common_F18_bugs
There is a new upgrade system for Fedora 18 making its first appearance in
Fedora 18 Beta. Upgrading via the system installer or the preupgrade tool is
no longer possible. To upgrade to Fedora 18 from Fedora 17, you should use the
new "Fedup" tool. Instructions and information on the new tool are here:
http://fedoraproject.org/wiki/FedUp. The tool is still under active
development, please take a look at the FedUp FAQ (in the wiki page) in case of
any issues with the upgrade process, and back up your system before trying the
*** Features ***
This release of Fedora includes a variety of features both over and under the
hood that show off the power and flexibility of the advancing state of free
software. Here are just a few of the new features:
= For users everywhere =
* Fedora 18 offers a brand-new version of the Gnome desktop, version 3.6,
straight from the upstream development process. Updates have also been made to
the KDE Plasma Workspaces, XFCE and Sugar]desktop environments; additionally,
the MATE desktop is available for the first time in Fedora.
* Fedora's new installer user interface enhances the anaconda installer with
improvements in ease of use and installation.
= For developers =
* This release includes several language updates, including the move to Perl
5.16, updating the Python 3 stack from 3.2 to 3.3, Rails 3.2 and updated D and
Haskell programming environments.
= For system administrators =
* Fedora 18 includes the final release of Samba 4, and can be used on an
Active Directory domain member out of the box. An integrated, new native
management software allows you to access data and server information easily.
* OpenStack in Fedora 18 has been updated to Folsom, the most recent release
by the OpenStack community. This Infrastructure-as-a-Service (IaaS) platform
enables the creation and management of cloud infrastructure.
* Eucalyptus 3.1, another IaaS platform, is available in Fedora for the first
time, and includes the major components of Eucalyptus.
* System Storage Management CLI tools simplify the user interface by
providing unified abstraction and interface for multiple storage technologies,
including lvm, btrfs and md raid.
For more Features, please take a look on the complete list:
*** Contributing ***
Great releases like Fedora 18 don't get made in a vacuum. We can't do it
without you! Bug reports are especially helpful as we move from the theory to
the applied physics. If you encounter any issues, please report them!
Fedora is a fantastic, friendly community, and we have many ways in which you
can contribute, including Documentation, Marketing, Design, QA, Development,
To learn how to help us, visit:
Thank you, and we hope to see you in the Fedora Project!
You may notice this announcement is a day late! We'd like to apologize to the
community for the delayed announcement and any consequences resulting from the
Join us on irc.freenode.net in #fedora-meeting-1 for this important
meeting, wherein we shall determine the readiness of the Fedora 18 Beta.
Thursday, November 22, 2012 @20:00 UTC (15:00 EST/12:00 PST/21:00 CET)
"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:
In the meantime, keep an eye on the Fedora 18 Beta Blocker list:
Btw. Thanksgiving conflict is known, but we decided not to move
Go/No-Go to Wednesday because of limited time for testing, let me
know in case of (strong) objections.
A new bugfix release of Bodhi has just been deployed to production.
Bugs and enhancement requests can be filed here:
Major user-facing changes in 0.9.3
- Bodhi will no longer alter the bug status if it is already VERIFIED
- Fixed grid pagination (Mathieu Bridon)
- Allow CLI users to enable automatic bug closing (Ralph Bean)
- Automatically submit updates that are edited with new builds back to
- Fixed Message-ID and X-Bodhi message headers (Till Maas)
- Publish messages upon buildroot override tag/untag (Ralph Bean)
- Don't trigger fedmsg notifications for internal bodhi or autoqa comments
Full list of changes
Luke Macken (25):
Sync up our specfic with rawhides
Fix an out of order changelog entry
Suppress tgmochikit, and include it in the one place that we actually need it.
Revert "Suppress tgmochikit, and include it in the one place that we actually need it."
The tooltip.css was merged into our main stylesheet
Move the deployment message to master.kid, and tweak the style
Don't send messages for internal bodhi comments
Don't send messages for autoqa comments
Fix the deployment status in the genshi template as well
Avoid calling fedmsg from our MashTask until it is thread-safe.
Don't add email headers for buildroot overrides
Reference the update in the Comment.__json__ for fedmsg
Revert "Reference the update in the Comment.__json__ for fedmsg"
Cast our SQLObject results set to a list
Revert "Avoid calling fedmsg from our MashTask until it is thread-safe."
import fedmsg helps
Require fedmsg 0.3.3+ for thread safety
Add the update_title to our Comment.__json__
Fix fedmsg requirement
Submit updates that are edited with new builds back to testing (#678)
Fix a typo
Handle cookielib.LoadErrors when initializing python-bugzilla.
Don't change the bug status if it is already VERIFIED (#698)
Bump version to 0.9.3
Mathieu Bridon (8):
Improved message after new Buildroot override
Prettify an error message
Fix unit test
Use the new TurboGears pagination parameter
The Fedora infrastructure moved to cgit
Make the 'Administration' button more useful
Only suggest candidate builds
Remove unused parameter
Patrick Uiterwijk (1):
Add different headers for different deployment types
Ralph Bean (8):
Some more fedmsg notifications.
Publish messages on buildroot_override tag and untag.
Merging. Agent information for fedmsg.
Allow CLI users to enable automatic bug closing.
Removed tools/fedmsg-watch.py (it was from *way* back in the day).
Change fedmsg topic from done to complete (for consistency).
fedmsg config values required for zeromq3.
Remi Collet (1):
Fix config for Apache >= 2.4
Till Maas (3):
Use a string for X-Bodhi-Update-Builds mail header
Fix generated message IDs
model: fix closing of bugs using bz._update_bug
Just a reminder to all, that barring any last minute issues Fedora 18
branched will enter freeze (again) starting tomorrow.
There will be one more stable push late tonight that will appear in
tomorrows branched compose, after that only updates fixing accepted Beta
Blockers or accepted Beta Nice to Have bugs will be allowed stable
until Beta is released.
Voting for the release name of Fedora 19 has begun. The pool of names
submitted by the community has been narrowed down to 8 possible names,
one of which will become the release name for the successor to Fedora 18
This vote began on November 9th, 2012, at 00:00 UTC, and will end at
23:59:59 on November 15th, 2012.
* We are using the Range Voting method
* If this is your first time using the voting system, you may want to
read the Fedora Elections Guide, located here:
* In order to vote, you must have a valid Fedora Project Contributor
Agreement (FPCA) on file and be a member of at least one non-CLA group.
Ballots may be cast on the Fedora Elections System here, now!
Today at FESCo meeting  it was decided to slip Fedora 18
Beta release by *two* weeks to give the Installer team,
the new upgrade tool and Secure Boot time to finish and
polish these features to meet our release quality standards.
As a result, Fedora 18 Beta will be pushed out by two weeks,
the development is re-opened, with tentative Change Deadline
on Nov 13. Fedora 18 Beta release is now Nov 27. Anyone with
objections to enter Beta freeze on Nov 13 can file a ticket
with FESCo on the Nov 12/13 and it will be discussed in the
ticket or on special meeting.
Final Change deadline is rescheduled to Dec 18 with final
Fedora 18 release on 2013 Jan 08 .
The Go/No-Go meeting on Thursday, Nov 08 is cancelled.
Please, work on your blocker bugs and help testing the
Fedora 18, so we will be able to release in the beginning