Fedora is a big project, and it’s hard to keep up with everything. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to each. Here are the five things for May 15th, 2015:
Countdown to the Fedora 22 release
Fedora 22 is currently scheduled to be released on May 26th — 11 days to go! This will include our Cloud, Server, and Workstation editions, along with other variants like Fedora Atomic (designed for running containerized apps) and of course KDE and Xfce desktop spins.
As always, the last few weeks before release are a little hectic as we iron out the last blocker bugs, but as of right now — knock on wood — the general sense is that we’re in pretty good shape. (We’ll know for sure by Thursday of next week, and hopefully sooner.) I know people sometimes get frustrated with schedule “slips”, and hopefully that won’t happen, but remember, a somewhat-elastic schedule is part of the plan for delivering high-quality releases (as Joe Brockmeier wrote last year).
If you’re feeling impatient, grab the F22 beta (Server, Cloud, or Workstation) and help us iron out any last-minute problems. As is usually the case, if you start with a Fedora beta release, you’ll be upgraded seamlessly to the final release when that comes out, so you won’t have to reinstall.
Fedora Marketing Status
Upcoming Video Meeting on “Three Editions”
That worked well, so we’re going to do it again this coming Monday, with Stephen Gallagher presenting on the official project objective which he’s leading, Fedora Editions, Phase 2. This is scheduled as a G+ event, plus we’ll have a text-based live transcription (and place for questions) in the
channel on Freenode IRC, and I’ll post the video in open video format webm/VP8 shortly after. We’re also planning a similar presentation from Fedora QA on June 8, and from various Fedora Engineering subteams in July.
FAD planning changes — impact!
A “FAD” is a “Fedora Activity Day” — a Fedora premiere event funded from our community budget. In order to make sure that this is spent most effectively, that we can communicate to our sponsors how we are making the most of their money, and that the rest of the community feels good about these allocations, we’ve rearranged the FAD organization process to focus on not just what will be done, but on the benefits of those activities to the project as a whole.
Priority for funding will be given to FADs which are directly connected to our 12-18 month community objectives. If you have an idea where getting a bunch of Fedora contributors together to work on something would have a big, positive effect on a current Objective, put together proposal. Or, if you have an idea for a new Objective which would have a big, positive effect on our mission in a well-defined timeframe (and know the right person to lead the work!), put together a proposal for that, too! (For either of these, contact the Fedora Council to start the discussion.)
Auto-update your systems with DNF
I was a sysadmin in a former life, and like many sysadmins, had more machines to maintain than one person could really give individual attention to. For many of those systems, I appreciated the ability to automatically apply updates without intervention. With Fedora 22, our command-line package tool switches from Yum to DNF, and Rackspace (and Fedora) hacker Major Hayden has a nice howto on his blog for configuring your system for automatic package updates with dnf.
With the pre-release crunch next week, 5tFTW will be taking a little break. I’ll be back the week after that.