Fedora 10 Beta: Cambridge's foundations are laid
Just on the heels of the Fedora Project's fifth anniversary, the Beta of
Fedora Linux version 10 (code-named Cambridge) is now available:
There is also a Beta contest! Test five things in the Beta that are
important to you as a user. If you find a bug *and* report it, you get
the free attention of a package maintainer on a problem personally
important to you!
Do your part to make Fedora 10 that much better.
Among the new, fun, and interesting features:
* New NetworkManager with connection sharing
* Improved printer handling
* Remote virtualization and easier virt storage
* Sectool, an auditing and security testing framework
* RPM 4.6, the first big RPM change in several years
... and more ...
* New version of PackageKit for managing software, with more fixes
and enhancements (which benefits all distributions)
* New version of PulseAudio (which benefits all distributions)
* Kernel 2.6.27, including better support for WiFi
* Better support for the EFI for Apple Macintosh hardware
* Faster graphical start-up by Plymouth, replacing the venerable
* Better support for webcams through the hard work in kernel
2.6.27 (which benefits all distributions)
* New icon theme "Echo", to be completed with the theme graphic
"Solar" in the Fedora 10 release
* Gnome 2.24
* KDE 4.1
* Adding the NetBeans IDE
* Eclipse 3.4
* Automatic installation of multimedia codecs
* Better HDTV support in X.org
* "Sugar" graphical environment (from OLPC) available for use,
testing, and development
A more complete list and details of each new cited feature is available:
For release information, including common and known bugs, please see our
Fedora -- Freedom² is a feature!
I'd like to invite testers and users to join #fedora-qa on Thursday,
September 25, 2008. Testing efforts will focus on testing Fedora 10
Beta Live images as well as system recovery using FirstAidKit.
Come with questions, bug reports, and/or suggested test areas.
More details will be posted to
After a week(end) of hacking, we're just not there yet for Beta. There
are a few more anaconda issues that we're tracking down:
* Network installs where network needs to be brought up in stage2
* Installs via Media
* Doing something with tracebacks
We're fairly confident that we've got fixes for these issues, but given
the current timeline we'd rather have a few more days of testing rather
than rush something out that doesn't work.
The Release Engineering team is recommending a slip of the Beta release
date to Tuesday Sept 30th. To go along with this slip, we recommend
that all further points of the Fedora 10 schedule slip out a week as
well, which would put the Fedora 10 release date at November 25th.
While we realize that this is a Holiday week for the vast majority of
people in the United States of America, the work for Fedora 10 would
have to have been completed by Nov 20th in order to release on the 25th
so there should not be (many) schedule conflicts. Any further slipping
of the schedule will slip around this holiday week.
FESCo will need to ACK this schedule change, and we are also making sure
this schedule doesn't conflict with (m)any thing(s) at Red Hat, and
other distributions. An announcement of the schedule change will be
made when it is fully approved.
Fedora -- Freedom² is a feature!
-------- Original Message --------
Subject: bugzilla.redhat.com, hardware.redhat.com Planned Outage |
09-17-2008 - 1700 EDT (-0400)
Date: Wed, 17 Sep 2008 15:00:29 -0400
From: Matthew Schick
O U T A G E R E Q U E S T F O R M
Severity One (Urgent)
1700 EDT (-0400)
Estimated Time Required:
Bugzilla and Hardware will be offline briefly.
New perl package will be installed to address performance
concerns. Mysql servers will be upgraded for bugfixes.
A kind reminder that shipped packages for which Fedora is upstream for
are **string frozen** since the Beta freeze of September 11: no
translatable strings can be added or modified for Fedora 10. For more
information, please refer to the F10 schedule and the string freeze
Also, please note that the Fedora L10n Steering Committee has moved
the Translation Deadline to 14/10 (one week earlier). Maintainers of
the above packages need to put a reminder to issue a new build *later*
than this date and before the Development Freeze of 21/10. The closer
to the development freeze the rebuild takes place, the better for our
translators. If you have not received any translations since the last
build, a rebuild is not necessary.
For more information concerning these two translation-related dates,
please refer to:
Feel free to drop an email to fedora-trans-list(a)redhat.com if you have
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
There will be an outage starting at Y2008-09-13 01:00 UTC, which will
last approximately 1 hour.
To convert UTC to your local time, take a look at
date -d '2008-09-13 01:00 UTC'
CVS / Source Control
Reason for Outage:
update koji to 1.2.6. it will enable us to turn garbage collection back on.
Please join #fedora-admin in irc.freenode.net or respond to this email
the status of this outage.
As of the rawhide compose last night, we are frozen for Fedora 10.
Rawhide will compose from the frozen content so that we all are aware of
what Beta is going to be comprised of. Extra scruitiny and testing of
rawhide over the next week is greatly appreciated. Builds that you feel
need to be in the Beta can be requested via the Release Engineering Trac
queue ( https://fedorahosted.org/rel-eng log in using FAS and file a new
ticket ). We'll want build n-v-r, rational of accepting the build, and
information about any testing you've already done with the build.
Lets all work together to make the beta freeze as quick and painless as
possible, and the Beta as useful as possible to greater Fedora 10
for more information.
Fedora -- Freedom² is a feature!
As many have already noticed, I performed a large bodhi upgrade recently. A
few weeks ago, during The Incident, I was forced to perform what was originally
going to be a week long bodhi migration and upgrade, overnight. During the
past two weeks I've pushed out 24 versions of bodhi to our infrastructure,
fixing various show-stoppers, and making sure that updates got out the door.
One of the most noticable changes is that bodhi is much more responsive.
Previously, bodhi was a single python process, running on a single server.
This single server was also responsible for composing the updates repositories,
and rawhide, among lots of other bodhi-related churn. This lead to much pain
and suffering for all.
The bodhi deployment has since changed. All bodhi requests are now load
balanced to a bunch of app servers, each running mod_wsgi with multiple bodhi
processes, each with multiple threads. All of the hard work is now done on an
isolated releng server. This separate bodhi "masher" is now responsible for
composing repositories, updating bugs, generating update notices, sending
emails, extended metadata generation, and calculating metrics. I also added
support for inter-bodhi communication, which allows our bodhi web frontends to
kick off push requests to our bodhi-masher instance.
Some of the new features in this release:
- A much more flexible karma automatism scheme. Stable/unstable karma
thresholds are now fully configurable
- Support for bug aliases
- A 'newpackage' update type
- Newer updates which obsolete older ones will now inherit their bugs and notes.
- A shiny new API in the fedora.client.bodhi module
- Lots of improved releng and security team support, making our lives little easier
- An improved `make update` template (be sure to update your Makefile.common)
- Some new bodhi-client features
- Creating updates for multiple releases using a single form
Note: This is not perfect yet. You can use the "New Update Form" to add any
number of builds for any number of releases, but bodhi will still create a
single update for each. This issue will be resolved in the next major bodhi
release, which will contain a full model redesign.
- updateinfo.xml generation takes about 20 seconds, instead of 20 minutes.
- A lot of metrics enhancements
- A ton of bug and usability fixes
Bodhi is far from being feature complete. Some new features in the pipeline:
- DeltaRPM generation
- Security issue (CVE) tracking and triaging
- Dependency closure verification, utilizing the power of rpmgrok.
- A complete remodeling from SQLObject to SQLAlchemy, which is almost complete,
will give us a lot more flexibility, speed, and power over our update model.
This will also allow for things such as having multi-builds for multiple
releases in a single update.
- File tickets here: https://fedorahosted.org/bodhi/newticket
- Help out here: https://fedorahosted.org/bodhi/report/1
- Subscribe to the bodhi mailing list here: https://fedorahosted.org/mailman/listinfo/bodhi
- You can always find bodhi here: http://bodhi.fedoraproject.org
Thank you all for your patience during the past few weeks,
p.s. If you're having issues with the bodhi client, a fixed version will be
going out with the next batch of updates. For the impatient, you can pull
fixed versions from koji (also, make sure your Makefile.common is up to date):
koji download-build --arch=noarch python-fedora-0.3.5-1.fc10
koji download-build --arch=noarch bodhi-0.5.2-1.fc9