From Fedora Project Wiki
m (Correct table header syntax) |
(Add a datetime column) |
||
| Line 4: | Line 4: | ||
{| | {| | ||
! Owner !! Task | ! Date/Time (if needed) !! Owner !! Task | ||
|- | |- | ||
| 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 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 | ||
|- | |- | ||
|} | |} | ||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
Revision as of 17:49, 12 May 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 |
|---|---|---|
| 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 |