No edit summary |
|||
Line 10: | Line 10: | ||
=== General === | === General === | ||
There is now a Fedora Updates policy<ref>[[Updates Policy]]</ref>, says<ref>http://rambleon.usebox.net/post/1209374581/fedora-updates-policy</ref> [[User:Jjmartinez|Juan J. Martínez]]. "I think it’s worth reading because, as the announcement says, it can be improved, clarified and adjusted; but it’s a very good starting point." | |||
[[ | And to ensure that updates can be installed smoothly, [[User:Wwoods|Will Woods]] explained<ref>http://qa-rockstar.livejournal.com/10187.html</ref> how the AutoQA process and depcheck<ref>http://qa-rockstar.livejournal.com/10368.html</ref> can be used "to be sure that they (Fedora update packages) don't have any unresolved dependencies that would cause yum to reject them (and thus cause everyone to be unable to update their systems and be unhappy with Fedora and the world in general." | ||
Former Fedora Project Leader [[User:Pfrields|Paul W. Frields]] has been transitioning<ref>http://paul.frields.org/?p=3416</ref> to a new role at Red Hat, "Operations Manager", but will still maintain an active presence in the Fedora community. "I realized the other day after a couple questions from friends in Fedora that maybe people were interested in what I was doing. I’m always surprised by that, but I’m happy to give some more details here." [[TomCallaway|Tom Callaway]] outlined<ref>http://spot.livejournal.com/315875.html</ref> some other transitions at Red Hat and the employment opportunities now available. [[User:Poelstra|John Poelstra]] has<ref>http://poelcat.wordpress.com/2010/09/30/want-to-be-the-next-fedora-program-manager/</ref> more details on the new "Fedora Program Manager" role. | |||
[[User: | |||
[[ | |||
[[User: | |||
<references/> | <references/> |
Revision as of 00:49, 12 October 2010
Planet Fedora
In this section, we cover the highlights of Planet Fedora[1] - an aggregation of blogs from Fedora contributors worldwide.
Contributing Writer: Adam Batkin
General
There is now a Fedora Updates policy[1], says[2] Juan J. Martínez. "I think it’s worth reading because, as the announcement says, it can be improved, clarified and adjusted; but it’s a very good starting point."
And to ensure that updates can be installed smoothly, Will Woods explained[3] how the AutoQA process and depcheck[4] can be used "to be sure that they (Fedora update packages) don't have any unresolved dependencies that would cause yum to reject them (and thus cause everyone to be unable to update their systems and be unhappy with Fedora and the world in general."
Former Fedora Project Leader Paul W. Frields has been transitioning[5] to a new role at Red Hat, "Operations Manager", but will still maintain an active presence in the Fedora community. "I realized the other day after a couple questions from friends in Fedora that maybe people were interested in what I was doing. I’m always surprised by that, but I’m happy to give some more details here." Tom Callaway outlined[6] some other transitions at Red Hat and the employment opportunities now available. John Poelstra has[7] more details on the new "Fedora Program Manager" role.
- ↑ Updates Policy
- ↑ http://rambleon.usebox.net/post/1209374581/fedora-updates-policy
- ↑ http://qa-rockstar.livejournal.com/10187.html
- ↑ http://qa-rockstar.livejournal.com/10368.html
- ↑ http://paul.frields.org/?p=3416
- ↑ http://spot.livejournal.com/315875.html
- ↑ http://poelcat.wordpress.com/2010/09/30/want-to-be-the-next-fedora-program-manager/