#15 Collaboration With QA Team for a Test Day / Week
Opened 5 months ago by nasirhm. Modified 10 days ago

We're in our final steps for the ISO Image and are working on the Change Proposal.

It's suggested to Organize Test Day / Test Week in collaboration with the QA team to ensure our spin works fine.


Metadata Update from @jflory7:
- Issue marked as depending on: #14
- Issue marked as depending on: #4

5 months ago

Metadata Update from @jflory7:
- Issue untagged with: blocked
- Issue priority set to: needs review (was: awaiting triage)
- Issue tagged with: help wanted, needs feedback, type - outreach

3 months ago

Metadata Update from @jflory7:
- Issue assigned to jflory7

3 months ago

Our Change proposal went through. We can move ahead with coordinating a Test Day with the support of the QA team. I have to admit… this is one thing in Fedora I have actually never done before!

@adamwill @sumantrom @coremodule @siddharthvipul1 Could any of you please point to documentation or share advice on how to coordinate a Test Day for the i3 Spin with the QA team in 2021? Where do we begin?

The i3 Spin Change was accepted by FESCo.

While things are looking all clear for us, I think this work should be blocked by getting official ISO builds in Fedora build infrastructure. A good deadline for this is Change Checkpoint: Completion deadline (testable) on Tue 2021-02-09 (see F34 key tasks schedule).

I am dropping my assignment on this ticket and marking this as depending on #29. Once #29 is resolved and we are building Fedora i3 Spin ISOs, we can start digging into the Test Day process and collaborate with the QA team.

Metadata Update from @jflory7:
- Issue untagged with: help wanted, needs feedback
- Issue priority set to: waiting on external (was: needs review)
- Issue set to the milestone: None (was: Fedora 34 Change Proposal deadline)
- Issue tagged with: blocked

2 months ago

Metadata Update from @jflory7:
- Issue marked as depending on: #29

2 months ago

Metadata Update from @jflory7:
- Assignee reset

2 months ago

Metadata Update from @jflory7:
- Issue set to the milestone: F34 – Change Completion deadline (testable)

2 months ago

Sorry, I kinda lost track of this with the shutdown. @sumantrom , can you please take care of this? Thanks!

I see the kickstarts aren't done yet...

Hey Folks

Sorry for all the delay here :(

I can take care of this. I will file it there and drop emails with further discussions about the test day to the change owners :)

@adamwill sorry, I missed this one.

Metadata Update from @jflory7:
- Issue set to the milestone: F34 – Beta Release Public Availability (was: F34 – Change Completion deadline (testable))

20 days ago

Metadata Update from @jflory7:
- Issue marked as depending on: #29
- Issue tagged with: blocked, type - outreach

20 days ago

@adamwill @sumantrom Thanks for following up. I updated this issue to the F34 Beta release milestone on 2021-03-16. We should have kickstarts submitted to composes by then.

We will keep an eye out for follow-up. We are happy to help out with organizing it if we can, just let us know how to be helpful.

@adamwill @sumantrom Thanks for following up. I updated this issue to the F34 Beta release milestone on 2021-03-16. We should have kickstarts submitted to composes by then.

We will keep an eye out for follow-up. We are happy to help out with organizing it if we can, just let us know how to be helpful.

@jflory7 we can have one around 1 week after 16th?
The last test day i18n is ending on 2021-03-15.

@jflory7 @nasirhm and et all involved here. I would like you guys to tell me a date or fixate on a couple. I am drafting up the test day schedule and I would like to have a placeholder for yours.

Login to comment on this ticket.