On Mon, Jan 14, 2019 at 12:45 AM Sumantro Mukherjee <sumukher@xxxxxxxxxx> wrote: > Usually 2-3 weeks after the GA, we tend to go ahead and call for test days > which is an email going out to all the teams and subteams notfing that we will > are accepting test day tickets for the upcoming release cycle. > We do have some fixed set of test day like GNOME, i18n , Cloud, Modularity, Upgrade > which run at different points in time from pre-beta to final accompanied with > the new changeset which needs testing. > We also have Kernel Test Day which is not realese bound and happens whever a new > Kernel releases which is every 8-10 weeks. The 'Create Test Days' can start off > after the Call for test days email is sent out and end about 2 weeks before the rain date. > Let me make sure I understand what you're saying. You want "Call for test days" to start earlier in the cycle and the create test days task to run until just before GA? So for example, if this was already changed for F30, the timeline would look like this: 2018-10-23 Preferred F29 GA target 2018-10-30 Alternate F29 GA target 2018-11-20 Call for F30 test days 2018-11-27 Create F30 test days (start) 2019-04-23 Create F30 test days (end) If that's not correct, can you please update my example timeline above? Thanks, BC -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
