tracker: F37 Test Day

[dustymabe]

Initial Tasks (to be done at least one week before test week)

• Open this ticket in the fedora-coreos-tracker repo
• Open a ticket with Fedora QA.
  • F36 example

To be done after the Fedora QA folks have taken action on the QA ticket:

• Confirm the Test Day page is created on the Fedora Wiki.
  • For example: https://fedoraproject.org/wiki/Test_Day:Fedora_36_CoreOS_2022-04-04
• Confirm the Test Day results app is created.
  • For example: https://testdays.fedoraproject.org/events/131
• Choose a day during the Test Week to host a video session for live debug help
• Setup a Google Meet or other video conference session
• Create a HackMD doc for capturing notes during live video session
• Find volunteers to enumerate new documentation + test cases required for Test Week
  • Best done via dedicated video session
• File an issue on fedora-coreos-tracker with TODO items.
  • For example: F36 FCOS Test Day TODO List #1147
• File a ticket requesting a Fedora badge is created
  • For example: https://pagure.io/fedora-badges/issue/871

Announcing Test Week

Should be completed after the Initial Tasks are done

• Draft an email to coreos@lists.fedoraproject.org announcing the Test Week

  • Include a link to the Fedora Wiki
  • Include a link to the Test Day results app
  • Include a link to fedora-coreos-tracker for Test Week
  • Include a link to the video conference
  • Include a link to the HackMD doc

• Cross-post announcement email to discussion.fedoraproject.org with #coreos tag

• Example format: https://hackmd.io/lCrVoW_RSMCRf2neiGhiPg

During Test Week

• Monitor fedora-coreos-tracker for new issues reported as part of Test Week
• Monitor #fedora-coreos on IRC for new issues reported as part of Test Week
• Ensure there is one or more representatives of Fedora CoreOS team present for live video session

After Test Week

• Update fedora-coreos-tracker ticket with any issues found
• Update fedora-coreos-tracker ticket with any documentation updates made
• Review Test Day results app and follow-up on any errors reported, if possible
• Follow up with the Fedora Badges ticket with Fedora Account System (FAS) usernames that participated in Test Week

[dustymabe]

I talked with Sumantro and we're going to target Thursday 09/22/22 for the F37 CoreOS Test day this cycle.

[jasonbrooks]

I opened the Fedora QA ticket: https://pagure.io/fedora-qa/issue/712

[dustymabe]

We discussed this at the community meeting today.

@jasonbrooks has stepped up and is going to help us organize this test day. Thank you @jasonbrooks!

[jasonbrooks]

@sumantro93 I believe we need action on our Fedora QA ticket to proceed with our checklist steps?

[jasonbrooks]

test day page and results app created:

https://testdays.fedoraproject.org/events/143
https://fedoraproject.org/wiki/Test_Day:Fedora_37_CoreOS_2022-09-29

[jasonbrooks]

FCOS 37 Test Day Live Debug Session
Thursday, September 29
Google Meet joining info
Video call link: https://meet.google.com/dsb-wixf-kqk
Or dial: ‪(US) +1 413-561-7664‬ PIN: ‪291 773 689‬#
More phone numbers: https://tel.meet/dsb-wixf-kqk?pin=2093097800113
Or join via SIP: sip:2093097800113@gmeet.redhat.com

HackMD for notes: https://hackmd.io/@xVKCtQRpTMqfkIvzfRIyRg/BkUKuQzWo/edit

[jasonbrooks]

For the checklist item "Find volunteers to enumerate new documentation + test cases required for Test Week," Dusty suggested we get together a video session to discuss these docs and test cases that we may want to add this time around.

For the F36 iteration of the test week (#1147), it looks like the people involved in volunteering for this were @mike-nguyen @sohankunkerkar @dustymabe @jlebon @aaradhak @davdunc @ravanelli @miabbott -- would any of you be interested in getting together this week to discuss ahead of the test day on the 29th? Also tagging @bgilbert.

[dustymabe]

Discussion Forum Post: https://discussion.fedoraproject.org/t/fedora-37-fedora-coreos-test-day-today/42798

[jasonbrooks]

request test day badge: https://pagure.io/fedora-badges/issue/890