Re: QA team schedule tasks
On Tue, Jan 29, 2019 at 9:01 PM Ben Cotton wrote: > Hi all, > > Here's a draft of the F31 QA schedule with your feedback incorporated: > > https://fedorapeople.org/groups/schedule/f-31/f-31-quality-tasks.html > > Please review it and let me know if anything looks amiss. You can > reply to this email or add a comment to the Pagure ticket at: > > https://pagure.io/fedora-project-schedule/issue/89 > > -- > Ben Cotton > Fedora Program Manager > TZ=America/Indiana/Indianapolis > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org Hey Ben, The test day bits look great. Thanks :) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: QA team schedule tasks
Hi all, Here's a draft of the F31 QA schedule with your feedback incorporated: https://fedorapeople.org/groups/schedule/f-31/f-31-quality-tasks.html Please review it and let me know if anything looks amiss. You can reply to this email or add a comment to the Pagure ticket at: https://pagure.io/fedora-project-schedule/issue/89 -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: QA team schedule tasks
On Mon, Jan 14, 2019 at 8:32 PM Ben Cotton wrote: > On Mon, Jan 14, 2019 at 12:45 AM Sumantro Mukherjee > 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? > Hey, Exactly that's what I meant. Thanks :) Thanks //sumantro ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: QA team schedule tasks
On Mon, Jan 14, 2019 at 12:45 AM Sumantro Mukherjee 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@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: QA team schedule tasks
On Sat, Jan 12, 2019 at 1:14 AM Ben Cotton wrote: > On Fri, Jan 11, 2019 at 12:43 PM Adam Williamson > wrote: > > > It would be useful to have the branch date / Bodhi activation point on > > the QA calendar, as that's an important date for us. It would similarly > > also be useful to have the Change deadlines on there. > > > That's an easy change. I'll add the QA flag to those entries. > > > The 'call for test days' and 'create test days' dates look like they > > don't match up with Sumantro's current practice; he can probably say > > how those should be rearranged. > > > They probably don't. Most of this has carried on relatively unchanged > for years, which is part of why I'm doing this now. > > Hey Ben, 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. > > The 'blocker meeting' dates are also kinda outdated; these days we run > > a blocker meeting any Monday we have enough bugs to review. Those can > > just be taken out. > > > Will do. > > > It would be good to have a 'Update blocker bug trackers' entry on the > > release date; this is the point at which the process documented in > > https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers should > > be done. > > > Will do. > > > ISTR that in the past the entries in the schedule could be links > > pointing to SOPs and so on. This would be really helpful. Am I > > misremembering and we never had this feature? Or has it been lost? > > > You remember correctly. I can add a single link to any task on the > calendar. Just let me know what links you want added to what tasks and > I'll include those. > > > Thanks, > BC > > > -- > Ben Cotton > Fedora Program Manager > TZ=America/Indiana/Indianapolis > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: QA team schedule tasks
On Fri, Jan 11, 2019 at 12:43 PM Adam Williamson wrote: > It would be useful to have the branch date / Bodhi activation point on > the QA calendar, as that's an important date for us. It would similarly > also be useful to have the Change deadlines on there. > That's an easy change. I'll add the QA flag to those entries. > The 'call for test days' and 'create test days' dates look like they > don't match up with Sumantro's current practice; he can probably say > how those should be rearranged. > They probably don't. Most of this has carried on relatively unchanged for years, which is part of why I'm doing this now. > The 'blocker meeting' dates are also kinda outdated; these days we run > a blocker meeting any Monday we have enough bugs to review. Those can > just be taken out. > Will do. > It would be good to have a 'Update blocker bug trackers' entry on the > release date; this is the point at which the process documented in > https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers should > be done. > Will do. > ISTR that in the past the entries in the schedule could be links > pointing to SOPs and so on. This would be really helpful. Am I > misremembering and we never had this feature? Or has it been lost? > You remember correctly. I can add a single link to any task on the calendar. Just let me know what links you want added to what tasks and I'll include those. Thanks, BC -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: QA team schedule tasks
On Fri, 2019-01-11 at 10:58 -0500, Ben Cotton wrote: > I am beginning to prepare the schedule for Fedora 31. One thing I want > to do is to make sure it still accurately reflects the work of > different teams within Fedora. Please look at the tasks on your team's > schedule [1] and discuss them in your team. Let me know if there are > tasks that should be added, removed, or modified. You can email me > directly or file an issue in Pagure[2]. > > I ask that you please provide feedback by Friday, 18 January, although > I will be able to incorporate changes after that. > > [1] https://fedorapeople.org/groups/schedule/f-30/f-30-quality-tasks.html > [2] https://pagure.io/fedora-project-schedule/issues So a couple of notes: It would be useful to have the branch date / Bodhi activation point on the QA calendar, as that's an important date for us. It would similarly also be useful to have the Change deadlines on there. The 'call for test days' and 'create test days' dates look like they don't match up with Sumantro's current practice; he can probably say how those should be rearranged. The 'blocker meeting' dates are also kinda outdated; these days we run a blocker meeting any Monday we have enough bugs to review. Those can just be taken out. It would be good to have a 'Update blocker bug trackers' entry on the release date; this is the point at which the process documented in https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers should be done. ISTR that in the past the entries in the schedule could be links pointing to SOPs and so on. This would be really helpful. Am I misremembering and we never had this feature? Or has it been lost? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
QA team schedule tasks
I am beginning to prepare the schedule for Fedora 31. One thing I want to do is to make sure it still accurately reflects the work of different teams within Fedora. Please look at the tasks on your team's schedule [1] and discuss them in your team. Let me know if there are tasks that should be added, removed, or modified. You can email me directly or file an issue in Pagure[2]. I ask that you please provide feedback by Friday, 18 January, although I will be able to incorporate changes after that. [1] https://fedorapeople.org/groups/schedule/f-30/f-30-quality-tasks.html [2] https://pagure.io/fedora-project-schedule/issues -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
