There was an outage starting at 2010-01-28 16:40:00 UTC, which is ongoing.
Resolution time is not yet known.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2010-01-28 16:40:00 UTC'
Affected Services:
Bodhi
Buildsystem
CVS / Source Control
Database
Fedora Account System
Fedora Community
Fedora Hosted
Fedora Package Database
Mail
Mirror System
Translation Services
Websites
Unaffected Services:
DNS
Torrent
Fedora Talk
Fedora People
Ticket Link:
https://fedorahosted.org/fedora-infrastructure/ticket/1951
Reason for Outage:
We are seeing a 25% packet loss to PHX2. This also is impacting
non-fedora systems like bugzilla and RHN.
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to
track
the status of this outage.
A friendly reminder that yesterday, January 26, 2010, we reached the
Feature and Spin submission deadline. Any new features or spins
submitted after yesterday will be targeted for Fedora 14.
A summary of the Fedora 13 milestones and exception process is here:
https://fedoraproject.org/wiki/Important_Release_Milestones
The next significant schedule milestone is Feature Freeze on February 9,
2010. At Feature Freeze it is expected that all features are
*significantly* "feature complete" and ready for testing.
https://fedoraproject.org/wiki/Feature_Freeze_Policy.
Features which are not significantly feature complete at Feature Freeze
will be reviewed on an exception basis by FESCo or deferred to Fedora 14.
Thank you,
John
p.s. If you have questions about our release processes or milestones
please reply to this email or contact me directly and I will be glad to
assist.
There will be an outage starting at 2010-01-21 11:00 UTC, which will last
approximately X hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2010-01-21 11:00 UTC'
Affected Services:
Websites
Buildsystem
Unaffected Services:
Bodhi
CVS / Source Control
Database
DNS
Fedora Account System
Fedora Community
Fedora Hosted
Fedora Package Database
Fedora People
Fedora Talk
Mail
Mirror System
Torrent
Translation Services
Ticket Link:
https://fedorahosted.org/fedora-infrastructure/ticket/1939
Reason for Outage:
Lost a switch blade this morning. A replacement is on the way.
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to
track the status of this outage.
A friendly reminder that the deadline for *submitting new features and
spins* for inclusion in Fedora 13 is coming soon!
>> Feature Submission: Tuesday, January 26, 2010 <<
>> Feature Freeze: Tuesday, February 9, 2010 <<
"At Feature Freeze all new features for the release should be
substantially complete and in a testable state, including enabled by
default if so specified by the feature. In the Fedora development
process, all new feature work is completed by Feature Freeze and tested
during the test releases: Alpha and Beta."
A summary of other important milestones in Fedora 13 is at this page:
https://fedoraproject.org/wiki/Important_Release_Milestones
Thanks for reading,
John
p.s. Please let me know if there are other special milestones or tasks
you would like to be reminded of.
p.s.s More information on these deadlines and freezes:
--Feature Submission: https://fedoraproject.org/wiki/Features/Policy
--Spins: https://fedoraproject.org/wiki/Spins_Process
--Feature Freeze: https://fedoraproject.org/wiki/Feature_Freeze_Policy
The boost maintainers have updated the boost package to the current
release (1.41.0) in rawhide for F13. More info here:
https://fedoraproject.org/wiki/Features/F13Boost141
Rebuilds for devel packages that require boost are mandatory, as SONAME
was bumped. Help from package maintainers with rebuilding packages with
boost dependencies is appreciated.
-benjamin
There will be an outage starting at Fri Jan 15 10:30:00 UTC, which is
ongoing.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d 'Fri Jan 15 10:30:00 UTC'
Affected Services:
Fedora People
Unaffected Services:
Buildsystem
CVS / Source Control
Database
DNS
Fedora Hosted
Fedora Talk
Mail
Mirror System
Torrent
Translation Services
Websites
Ticket Link:
https://fedorahosted.org/fedora-infrastructure/ticket/1930
Reason for Outage:
The xen host fedorapeople is on is currently not responding to pings.
I've contacted the hosting provider but have not heard back yet. It is
unclear when this host will be back online.
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to
track the status of this outage.
If you're the maintainer of a cmake-based package, and use the %cmake
macro, be aware I just implemented a change in rawhide (to
cmake-2.8.0-2) to drop the usage of
-DCMAKE_SKIP_RPATH:BOOL=ON
as previously discussed(1).
If you want or need to continue with the old behavior, use
%cmake %{?_cmake_skip_rpath}
NOTE: At the time of writing this, kde4 packages that use the
%cmake_kde4 macro still use %{_cmake_skip_rpath} by default (at least
until we can sort out other rpath-related issues in kde4's buildsystem).
Thanks.
-- Rex
(1) See also,
http://lists.fedoraproject.org/pipermail/devel/2009-October/thread.html
There will be an outage starting at 2010-01-13 22:00 UTC, which will last
approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2010-01-13 22:00 UTC'
Affected Services:
Fedora Hosted
Unaffected Services:
Buildsystem
CVS / Source Control
Database
DNS
Fedora People
Fedora Talk
Mail
Mirror System
Torrent
Translation Services
Websites
Ticket Link:
https://fedorahosted.org/fedora-infrastructure/ticket/1926
Reason for Outage:
hosted1.fedoraproject.org (the primary fedorahosted host) has been
throwing memory errors so we have a ticket open to fix it. There is a 4
hour window for them to work on it though it's not likely to be down that
whole time so the actual outage should be much smaller.
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to
track the status of this outage.