As seen on the official announcement list, the final release of Fedora 13 will be postponed by a one-week slip. As the announcement notes, the blocker bug list is not empty, which means that according to our F13 final release criteria, we slip the release.
It's always disappointing when we don't hit our original target, but these criteria allow us to focus on objective markers to measure our readiness. It was a pleasure sitting in that readiness meeting tonight with some very smart people, because it was focused on the worthy goal of dispassionately measuring our status based on the ruler we've set for ourselves.
I suspect as we go we'll need to tune release criteria in certain areas where we want more detail. Tonight, for intance, we found there was at least one place where the written criteria could be clearer about their intent. There is a retrospective scheduled for QA after the release of Fedora 13, at which we can note some of the discrepancies and tune as needed.
This iterative approach has worked very well for our release schedule, which I'd really like to see us let stand for a few releases, as we consider other changes. Thanks to all of the people who participate in the process — the teams of people working on QA, Release Engineering, Anaconda, kernel, and countless other packages for our release. The collaboration that's gone on this release has been tremendous, and Fedora 13 is shaping up to be spectacular as a result!
I’m running it here and would encourage contributors and early adopters to try it out. We could really use your help in finding remaining bugs so we can squash them before the Beta release near the end of this month. You can find a list of common bugs on the wiki as well.
The big day is here — Fedora 12 is released, uniting freedom, technology, and community. You can download the all-natural goodness at http://get.fedoraproject.org and read some of the highlights of the release. The official announcement text is here, and on the wiki as well.
I’m a big fan of the new Abrt tool which can produce and file detailed information for developers in a Bugzilla bug with just a few clicks, and also the improvements to the SELinux Troubleshooter, which do essentially the same thing. Thanks to Fedora’s strong stance on freedom, this release features some of the best free video drivers yet. On all three of my home machines that use NVidia and ATI cards, kernel mode setting, the enhanced graphical boot display, and on-the-fly display setting work like gangbusters — no more proprietary drivers causing problems we can’t debug or fix. (Thanks Nouveau and Radeon guys.)
The latest GNOME and KDE sparkle, Bluetooth tethering and audio are no-brainers, mobile broadband is dead-simple, PulseAudio happily converses and integrates with everything including your PlayStation3 and probably even your kitchen sink, PackageKit can install missing commands at the shell… Oh, and did I mention the virtualization features? It’s sheer heaven for sysadmins and techie types who love to try different distros; just install them in Fedora’s built-in KVM and go to town!
And of course there’s plenty for developers, including the latest Eclipse and NetBeans IDEs, and an updated SystemTap that helps trace and locate opportunities to optimize code. And of course you can get compilers and tools galore, and all the frameworks, libraries, and modules you need to build powerful applications in any language you prefer, including cross-compiler support for building Windows executables on Fedora.
Fedora 12 also features a nice helping of fit and finish on the Desktop, with fresh theming, easier to navigate panels and menus, tooltips that give you useful information while intelligently staying out of your way, and more useful notifications that are also reduced in frequency to keep the most important information in front of you at all times.
In short, it’s our best release ever, and you should download it and give it a try today!
Some important statistics from the first week of Fedora 11 release:
Note that our expert Fedora Infrastructure team made all this traffic almost unnoticeable to people, instead of crushing our servers to their knees. Hopefully Mike McGrath and some of the other team members will post a little bit about how they pull all this off. (Hint, hint!) I know that we use memcached, and that MirrorManager, maintained by Matt Domsch, figures heavily into our ability to get people to the closest Fedora bits when they request a download.
It never ceases to amaze me that our releases don’t seem to cause meltdowns like they used to. I think the Infrastructure team secretly yearns for release days to be more exciting, but it’s ironic that their own success makes that less likely.
[This post was supposed to be out yesterday, but somehow I managed to brush my touchpad the wrong way and… well, the dog ate my homework. Or WordPress did. Either way, sorry about the lateness of the hour, and all that. Revised now for more contemporary enjoyment. — Ed.]
Yes, that 300 joke isn’t getting any funnier. But it’s not getting any older either! Well OK, maybe it is, but remember that “beta” works just as well there, so you may have to endure it one more time, sorry.
Anyway, yesterday our Fedora 11 Alpha release hit the wires, and they are humming hotly even as we speak with flying bits. We’ve provided a brief set of release notes where you can see some of the major changes called out.
I often get questions from people asking, what’s the point of an Alpha anyway? Well, essentially it’s to ensure we can effectively compose a Fedora release that can be installed by most people, and once that’s done, to give our community a chance to test the current state of features from a known starting point. Testing is, in fact, our focus once an Alpha release of Fedora is out the door, and every bug you file can make a big difference in the quality of the final Fedora release.
Typically people will install Fedora 11 Alpha on a test machine, and then update to the latest Rawhide packages. You see, Rawhide, our development branch of Fedora, keeps moving after we’ve started working on an Alpha release, so some bugs might be fixed with that update. On the other hand, you might also see totally new ones. It’s very early in the development cycle, so don’t expect a Fedora 11 Alpha system to necessarily be ready for your daily non-testing use (although I do know people who essentially run on the development branch almost all the time, and my hat’s off to them).
The point is, once you have your system running, we’d love to receive bug reports from you. That helps us eradicate problems early and provide a better release by the time the Beta, Preview, and final emerge.
Interestingly, there were hardware-specific bugs in previous releases reported by numerous people that could have easilly been found, had someone taken time to test an Alpha installation or boot on their hardware. So by testing, you really can be a big help to the overall Fedora community! You can often file bug reports straight from the installer, for instance, if your network hardware is supported. You can also use our helpful wiki page to learn how to file a bug. By the way, if you find a problem on that page, you can use its discussion page to tell us what needs improvement.
Basically, it’s a great time to try out the beginnings of Fedora 11 with our Alpha release, and let us know how you fare. And when you do, you’re part of the enormous (and still growing) Fedora community.