Fedora 13 Release Candidate phase coming soon
by Jesse Keating
We will be entering the Release Candidate phase of Fedora 13 development
in one week's time.
What does this mean? It means that we will have hopefully reached a
point where all known release blockers¹ have been fixed and we are read
to compose the final release tree. The only changes accepted from this
point on will be changes deemed important enough to delay the release
should we not get them fixed in time. It also means we will be opening
up bodhi for preparing 0-day updates for Fedora 13, changes which are
not important enough to delay the release. This means that updates put
into bodhi and marked as "stable" will go to the stable updates
directory, not Fedora 13 itself.
If you have a change that you feel is critical to the release, make sure
your bug blocks F13Blocker so that it will get the attention of the
release team. Builds that fix issues on the blocker will be hand picked
into the release and will bypass the bodhi stable phase.
This is the first time we'll be doing this phase of the development in
the new No Frozen Rawhide style of development, so there are bound to be
a few hiccups, and we are still drafting a wiki page to explain this
phase of the development. Please bear with us as we work together to
get Fedora 13 out the door.
¹)
https://bugzilla.redhat.com/showdependencytree.cgi?id=507681&hide_resolved=1
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
13 years, 7 months
Recent Bugzilla Comment Concerning Fedora 11 EOL
by John Poelstra
All open Fedora 11 bugs recently received a comment warning about the
upcoming end of life for Fedora 11. This email serves as correction to
part of that notification.
Due to an error on my part this warning was sent out earlier than it
should have been. The statement "Approximately 30 (thirty) days from
now Fedora will stop maintaining and issuing updates for Fedora 11..."
is incorrect. The end of life (EOL) for Fedora 11 will be June 18,
2010, which is thirty days after the release of Fedora 13, currently
scheduled for May 18, 2010. When Fedora 11 reaches EOL at that time,
bugs open for Fedora 11 will be closed as previously described.
For more information on Fedora's policy for maintenance of our releases,
please refer to:
http://fedoraproject.org/wiki/LifeCycle#Maintenance_Schedule
My apologies for any inconvenience or confusion this error may have caused.
John
13 years, 7 months
Elections - nominations open Sat 2010-04-24
by Paul W. Frields
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
With a Fedora release coming soon, it's also time for Fedora
Elections. Both the Fedora Project Board and the Fedora Engineering
Steering Committee (FESCo) will have open seats during this election
cycle.
Nominations for these seats open tomorrow, Saturday, April 24, 2010.
You can nominate yourself, or someone else. It's recommended that if
you intend to nominate someone else that you consult with that person
first. The entire election schedule, and other important information
for all nominees, is posted on the wiki's main Elections page, and the
specific nomination pages for the Board and FESCo:
https://fedoraproject.org/wiki/Elections
https://fedoraproject.org/wiki/Board_nominations
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
You can also find more information about both these at their main wiki
pages:
https://fedoraproject.org/wiki/Board
https://fedoraproject.org/wiki/FESCo
Please thoughtfully consider how you can best contribute to Fedora by
serving on one of these important committees, or encourage someone you
know who can make a difference to serve. Thank you!
- --
Paul
(25 days to Fedora 13!)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iD8DBQFL0huhrNvJN70RNxcRAi+2AKDN36pLiBgca75+PoNkpx/30av/lACePcSE
5tfX27I9Mxbs/JmGrRTuNOM=
=WQTH
-----END PGP SIGNATURE-----
13 years, 7 months
Request for Comments: Fedora Project Contributor Agreement Draft (Replacement for Fedora Individual Contributor License Agreement)
by Tom Callaway
Hello Fedora! (Is this thing on?)
Sorry for the very wide net, but we wanted to make sure as many members
of our community could see this as possible.
For some time now, Fedora has been working with Red Hat Legal to come up
with a replacement for the Fedora Individual Contributor License
Agreement (aka, the Fedora ICLA). As a result, the Fedora Project
Contributor Agreement (FPCA) has been approved by Red Hat Legal, and is
now being presented to the Fedora Community for comments and discussion.
The full text of the FPCA, along with a FAQ, can be found here:
https://fedoraproject.org/wiki/Legal:Revised_Fedora_CLA_Draft
Please, take a moment and read the FPCA and the FAQ. It is not a long,
or overly complicated document, as legal documents go, but it is
important that all Fedora Contributors read it over and make sure they
understand it and like it (or can at least agree to it).
Fedora Legal wishes to give the Fedora community a window of time for
discussion and review of the FPCA. This window is open until May 18,
2010 (2010-05-18). After that point, either a revised FPCA will be
released for review, or we will begin the process of phasing in the FPCA
and phasing out the Fedora ICLA.
Thanks in advance,
Tom "spot" Callaway, Fedora Legal
P.S. Fedora Legal would like to give a huge thank you to the people
involved behind the scenes to make the FPCA possible. The primary author
was Richard Fontana, with feedback from Tom Callaway, Pamela Chestek,
Paul Frields, and Robert Tiller. Feel free to give them gifts (for
example, drinks or tasty snacks) as thank yous, although, this is not a
requirement (legal or otherwise). ;)
13 years, 7 months
Fedora 13 bodhi updates cleanup
by Bill Nottingham
We've had a couple of issues with F13 updates where multiple
versions of a package had updates-testing requests filed in
bodhi at once, causing the 'wrong' update to be pushed to
final.
Becuase of this, I'm going through and cleaning out some
of the cases where we have multiple live test updates for
a package so we don't run into this again. Apologies for
any mails you get from bodhi about this.
In the near future, we will re-enable the bodhi auto-obsoletes
code so we won't hit this problem. You can also avoid the
issue by making sure you unpush/delete older updates yourself
when issuing new ones, or by just editing the older update and
changing the package.
Thanks for the understanding,
Bill
13 years, 7 months
