From Fedora Project Wiki

(update)
(update)
 
(2 intermediate revisions by 2 users not shown)
Line 5: Line 5:
{|
{|
! Date/Time (if needed) !! Owner !! Task
! Date/Time (if needed) !! Owner !! Task
|-
| Anytime post-freeze || Toshio || Change PackageDB build acls to Obsolete.  We don't acl the builds and we're never going to so get rid of this in the db
|-
| Anytime || Kevin || move vm's off xen14 and retire it. It's going out of warentee
|-
| 2011-06-21 || kevin || post release housecleaning tasks.
|-
| 2011-06-23 || everyone || FPCA drop dead date. Need to clean up issues from this at that time.
|-
| 2011-06-24 || everyone || F-13 end of life date.
|-
| 2011-07-01 || everyone || blogs.fedoraproject.org end of life.
|-
|-
| 2011-07-11 to 2011-07-14 || smooge and nirik || out on site in PHX2.  
| 2011-07-11 to 2011-07-14 || smooge and nirik || out on site in PHX2.  

Latest revision as of 15:35, 9 July 2011

Fedora Infrastructure freezes changes to certain critical boxes when we near a release (alpha, beta, prerelease, as well as final release). This is to ensure that the build system, compose system, download servers, and other infrastructure for creating and hosting the release are stable for the release date. Naturally, some tasks that we come up with during this time are held off on until after the release. This page is a short list of things that are planned for post freeze so we think about them then.

Fedora 15 final freeze

Date/Time (if needed) Owner Task
2011-07-11 to 2011-07-14 smooge and nirik out on site in PHX2.

See also fedora-infrastructure git repo for ics / ical files:

http://git.fedorahosted.org/git?p=fedora-infrastructure.git;a=blob_plain;f=calendars/infrastructure-upcoming.ics;hb=HEAD