On Tue, 2010-10-05 at 11:23 -0400, John Poelstra wrote: > Adam Williamson said the following on 10/04/2010 05:20 PM Pacific Time: > > On Sun, 2010-10-03 at 14:49 -0400, John Poelstra wrote: > >> Start End Name > >> Tue 28-Sep Mon 18-Oct Beta Testing > >> Thu 07-Oct Wed 13-Oct Pre-RC Acceptance Test Plan > >> Fri 08-Oct Fri 08-Oct Final Blocker Meeting (f14blocker) #3 > >> Mon 11-Oct Fri 15-Oct Daily Review& Notification of Open Final > >> Blocker Bugs > >> Tue 12-Oct Tue 19-Oct Test 'Final' Test Compose > >> Fri 15-Oct Fri 15-Oct Final Blocker Meeting (f14blocker) #4 > >> Mon 18-Oct Mon 18-Oct End of Beta Testing > >> Mon 18-Oct Mon 18-Oct Final Blocker Meeting (f14blocker)--Blocks RC > >> Compose > >> > >> How has schedule worked out for your team during Fedora 14? > >> > >> The schedule is only as good as the information I receive so if you've > >> noticed things that would work better for Fedora 15, please add them to > >> https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective > > > > I'm a bit confused that the TC hits on 12th but the change deadline > > (freeze) is the 18th. That means a lot of change can land between TC1 > > and RC1 and make TC testing almost irrelevant... > > > This is the same approach we have taken for the Fedora 14 Alpha and > Beta. Feel free to add to the restrospective page if you think we > should do this different in the future: > https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective To add some extra flavor, when we originally added the 'test compose' check-point to get earlier media-based testing prior to RC, we recognized that it occurs prior to the freeze. So there is always risk associated with accepting critpath/distruptive changes after the compose, and before freeze. In fact, this has been a contributing factor to slips in the past (see https://fedoraproject.org/wiki/Fedora_13_QA_Retrospective#Could_have_been_better). I'd like to believe that with additional proventester process and scrutiny, along with using bodhi for in-development releases, we mitigate the risk, but not not remove it. Definitely keep an eye out for obvious gotchas, noting on the appropriate retrospective wiki (schedule [1] or QA [2]). Thanks, James [1] https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective [2] https://fedoraproject.org/wiki/Fedora_14_QA_Retrospective
Attachment:
signature.asc
Description: This is a digitally signed message part
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
