Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
have anything important for the agenda, so let's give folks a break
before the blocker review meeting!
If you're aware of anything it would be useful to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
# F36 Blocker Review meeting
# Date: 2022-03-14
# Time: ** 16:00 ** UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 2 proposed Beta blockers, 1 proposed Beta freeze
exception issue, and 4 proposed Final blockers to review, so let's
have a review meeting on Monday.
Note that DST starts in North America on Sunday, so the meeting time in
UTC is now an hour earlier than before. If your region uses daylight
savings time and it starts this weekend, the meeting will be at the
same local time as usual. If your region does not use DST, or it
doesn't kick in yet, the meeting will be an hour earlier in local time
than usual. Use `date -u` to check the current UTC time if you're
unsure.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F36 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
# Fedora Quality Assurance Meeting
# Date: 2022-03-14
# Time: ** 15:00 ** UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat
Greetings testers!
It's been a couple of weeks since we met, so let's get together and
see where we're at for Fedora 36 and so on.
Note that DST starts in North America on Sunday, so the meeting time in
UTC is now an hour earlier than before. If your region uses daylight
savings time and it starts this weekend, the meeting will be at the
same local time as usual. If your region does not use DST, or it
doesn't kick in yet, the meeting will be an hour earlier in local time
than usual. Use `date -u` to check the current UTC time if you're
unsure.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 36 status
3. Current criteria / test case proposals
4. Test Day / community event status
5. Open floor
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
Due to outstanding blocker bugs[1], we do not have an F36 Beta RC. As
a result, F36 Beta is NO-GO by default and today's Go/No-Go meeting is
cancelled.
The next Fedora Linux 36 Beta Go/No-Go meeting[2] will be held at 1700
UTC on Thursday 17 March in #fedora-meeting. We will aim for the
"target date #1" milestone of 22 March. The release schedule[3] has
been updated accordingly. This change does not impact the final
release date.
[1] https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist
[2] https://calendar.fedoraproject.org/meeting/10209/
[3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Hey Folks,
As most of you already know, we have the i18n test week happening now.
If you are someone who loves to experience Fedora Linux in your native
language and test out the new i18n changes this is your moment.
The wiki [0] starts off by telling you what the test day is all about,
the test day result page[1] has the test cases which can be executed
during this test week!
Happy Testing!
[0] https://fedoraproject.org/wiki/Test_Day:2022-03-08_I18N_Test_Day
[1] https://testdays.fedoraproject.org/events/127
PS : If you have questions, reach out to the @test list or the
#fedora-test-day on libera
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
have anything important for the agenda, so let's give folks a break
before the blocker review meeting!
If you're aware of anything it would be useful to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net