#686 Fedora 36 Beta validation test event
Closed: Wontfix 2 months ago by adamwill. Opened 2 years ago by adamwill.

This is an idea from the F35 QA Retrospective, based on a suggestion from @kparal . He wrote "After F34, we talked in our team about doing a selected compose testing in a complete full run (all test cases), way ahead of the milestones (Beta and Final), and as a group effort to encourage people to really fill out all test cases. Yet we never got to it in F35. Some of the bugs might've been discovered earlier this way."

My idea is to have a test event (test day, test week, whatever) for this around Beta freeze, and again around Final freeze, assuming it works well at Beta. We would just pick a time slot and promote the event, and then link to the latest nominated nightly validation page for actually taking part, I guess. The main thing would be to treat it like an 'event' with an announcement mail and folks hanging out on IRC and so on. The goal would be to get as close as possible to full coverage of the validation tests for the nightly, and of course report and nominate any blocker/FE bugs.

@sumantrom , @kparal , would you be interested in organizing this? Thanks!


This is an idea from the F35 QA Retrospective, based on a suggestion from @kparal . He wrote "After F34, we talked in our team about doing a selected compose testing in a complete full run (all test cases), way ahead of the milestones (Beta and Final), and as a group effort to encourage people to really fill out all test cases. Yet we never got to it in F35. Some of the bugs might've been discovered earlier this way."

My idea is to have a test event (test day, test week, whatever) for this around Beta freeze, and again around Final freeze, assuming it works well at Beta. We would just pick a time slot and promote the event, and then link to the latest nominated nightly validation page for actually taking part, I guess. The main thing would be to treat it like an 'event' with an announcement mail and folks hanging out on IRC and so on. The goal would be to get as close as possible to full coverage of the validation tests for the nightly, and of course report and nominate any blocker/FE bugs.

@sumantrom , @kparal , would you be interested in organizing this? Thanks!

I am planning to start a thread on @test talking about this idea. Roll it out to folks in the community blog and then organize a test day. As a trail run, I wanted to run a rawhide validation event (just for kicks). This will help us understand, what more to plan for. How does it sound to you @kparal and @adamwill ?

Sure, we could do that. Maybe in January?

Sure, we could do that. Maybe in January?

Sure. I would love to. I am probably going to still work on a draft document piece that everyone can review when people are back!

Great idea, Couldn't agree more, I also really enjoy doing Release validation tests +1

well, it's a long way past F36. this is still probably a good idea. should we try and do it regularly in future cycles? I think we did do this at least one time since...

Metadata Update from @adamwill:
- Issue close_status updated to: Wontfix
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata