FESCo today approved a change to how orphan and deprecated packages are
handled in Fedora.
The prior policy was:
- Packages that have been orphaned for more than three months require
a re-review, regardless of whether or not they have been blocked.
The new policy is:
- Any package that is deprecated (i.e., blocked) requires a re-review
before it can return to Fedora. Orphaned packages do not require
Note that orphaned packages will be deprecated once per release cycle.
For more information, see:
Bill, on behalf of FESCo
This is a reminder email about the end of life process for Fedora 13.
Fedora 13 will reach end of life on 2011-06-24, and no further updates
will be pushed out after that time. Additionally, with the recent
release of Fedora 15, no new packages will be added to the Fedora 13
Please see http://fedoraproject.org/wiki/DistributionUpgrades for more
information on upgrading from Fedora 13 to a newer release.
Frontend Web/Client Changes
* Buildroot Override Management
* Make update notes mandatory (fesco#457)
* Gracefully handle invalid update template values (#597)
* Fixed a bug that would prevent people from editing updates
* Support blacklisting certain users from receiving bodhi emails (for autoqa)
* More robust handling of 'pending' koji tags (#594)
* More configurable for non-Fedora deployments
* Added more metrics to our report generator
* # of updates that reach the stable karma threshold
* # of updates that spent the minimum time in testing
* # of proventester karma types
* output: https://fedorahosted.org/fesco/ticket/517#comment:5
* Optimize our 'list' API when querying updates by bug number (#610)
* Support adding comments without triggering email notifications (to prevent AutoQA spamming)
I'm happy to announce the results of our recent round of elections for
at-large seats on the Fedora Board and FESCo, and FAmSCo. The results
are as follows:
There were five FESCo seats up for election this cycle. A total of
200 ballots were cast in the FESCo election. Each of the eight
candidates could receive up to 1600 votes (200 ballots multiplied by 8
Votes | Candidate
1120 | Kevin Fenzi (nirik)
1020 | Bill Nottingham (notting)
764 | Tomáš Mráz (t8m)
699 | Peter Jones (pjones)
567 | Stephen Gallagher (sgallagh)
535 | Kyle McMartin (kylem)
480 | Justin Forbes (jforbes)
398 | Iain Arnell (iarnell)
The top five candidates were Kevin, Bill, Tomáš, Peter, and Stephen.
Each will server a full two-term position on the Fedora Engineering
* * * * *
There were three open seats on the Fedora Board this election cycle. A
total of 204 ballots were cast. Due to the system of range voting
that we use in Fedora elections, this means that each of the six
candidates could receive up to 224 votes (204 ballots multiplied by 6
Votes | Candidate
833 | Rex Dieter (rdieter)
608 | Jon Stanley (jds2001)
607 | Peter Robinson (pbrobinson)
421 | Robert 'Bob' Jensen (EvilBob)
367 | Andrea Veri (averi)
274 | Zach Oglesby (zoglesby)
I'm pleased to have Rex and Jon return as members of the Board, and
welcome Peter to the Fedora Board as well. All three of these
individuals will serve full two-term positions on the Fedora Board.
Fedora Project Leader
Sorry for the late notice, though I did trail this a bit last week.
Tomorrow we're having a special Test Day, out of the usual Test Day
cycle (which will open for F16 in a few weeks), for World IPv6 Day.
Special thanks to Linda Wang for getting the ball rolling on this. You
can find the event page at:
with full instructions on testing, including getting IPv6 set up, either
natively or through various tunnel providers. You don't need Rawhide for
testing, Fedora 15 is fine. I know IPv6 is scary to many (including me),
but look at this as an opportunity to help Fedora's IPv6 readiness while
learning about IPv6 from people who know what they're talking about! I
know that's what I'll be doing. The Test Day is in #fedora-test-day on
Freenode, all day long. Fedora QA and Linda's team will be there to help
with testing. Thanks everyone!
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
The Fedora Board consists of five elected seats and four appointed
seats. In this elections cycle, there will be two openings for
appointed Board seats and three opening for elected Board seats. As
part of the normal Board succession process, one Board appointment
is made before Board elections and the other is made after the
I'm happy to announce that Guillermo Gomez has accepted the
responsibility of serving on the Fedora Board. Guillermo has
demonstrated his commitment to Fedora through his tireless efforts on
a number of different fronts, including working on packaging,
development, and ambassador programs. He has also shown his ability
to mentor new contributors and help grow the Fedora community. I have
no doubt that he'll continue these efforts while on the Board, and
that he'll bring his perspective to help the Board as it makes
decisions affecting the direction that Fedora takes. I would like to
publicly thank Guillermo for his willingness to serve, and I hope the
entire Fedora community will join me in welcoming him to the Board.
Guillermo will fill seat A4 (see the Board History for a list of
the seats), which has been held by Stephen Smoogen for the past year.
I'd also like to take this opportunity to publicly thank Stephen for
the work he's done on
behalf of the Fedora Board.
Elections for the three open elected seats on the Board (as well as
FESCo elections) will begin on June 2nd at UTC 0001, as shown on the
Fedora wiki's Elections page. All community members are encouraged
to cast their vote until the elections close at the end of the day
(UTC time) on June 8th. Within a week or two of the end of elections,
another appointment will be made for the remaining Board seat (seat
A3). If you have interest in serving on the Fedora Board, please
don't hesitate to contact me directly to indicate your willingness to
Fedora Project Leader
During reboots and updates yesterday, the filesystem for the
buildsystem was written to from two seperate places at the same time.
A snapshot was taken of the filesystem and a fsck started.
Builds were completing normally and the filesystem was functioning,
until about 08:11UTC when the filesystem switched to read-only.
Builds since that time have failed.
We have disabled the builder hosts for now (submitted jobs will queue
up and wait for their return) until the file system check is completed.
You can follow progress of this issue in:
Sorry for the inconvenience.