Skip to content

tracker: F43 Test Week #2018

@yasminvalim

Description

@yasminvalim

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


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.
  • Confirm the Test Day results app is created.
  • Confirm the Test Week calendar event is created
  • File an issue on fedora-coreos-tracker with TODO items.
  • 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 a ticket requesting a Fedora badge is created

Announcing Test Week


Should be completed after the Initial Tasks are done

  • Draft an email to [email protected] 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 Matrix 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

Metadata

Metadata

Assignees

Labels

F43jirafor syncing to jira

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions