2022-11-28 @ **16:00** UTC - Fedora QA Meeting
by Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2022-11-28
# Time: **16:00** UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat
Greetings testers!
It's time for a first meeting since Fedora 37 was released! Let's get
together to check in on 37 and 38.
Note that clocks have now gone back everywhere that does daylight
savings time, so the meeting will be at 16:00 UTC (I'm almost sure I
got this right this time). If your clocks changed a while back, the
meeting will be at the same local time as always. If your clocks didn't
change, the meeting will be an hour later in your local time than it
was during the summer.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
Note, this may possibly be the last meeting of the year - we may cancel
the meetings in December as a lot of RHers will be on vacation and it's
a pretty slow time of year.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 37 review, Fedora 38 check-in
3. Test Day / community event status
4. Open floor
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 3 months
Re: Proposal: make meetings officially every other week
by Adam Williamson
On Fri, 2022-10-28 at 17:42 -0700, Adam Williamson wrote:
> Hey folks!
>
> The more attentive among you may have noticed I've had a kinda
> unofficial policy of holding the QA meetings every other week for a
> while. We just don't seem to have as much to discuss/debate as maybe we
> did five or six years ago. I choose to see this as a positive sign that
> everything is working smoothly, but maybe others disagree? I dunno.
>
> Anyway, it seems a bit silly that we still notionally schedule a
> meeting every week but I almost always cancel half of them. So I'm
> proposing we make it official that we only meet every *other* week.
> This would save sending out cancellation notices and manually canceling
> the event in the calendar every other week.
>
> What do folks think? Makes sense? Or would you rather we really do meet
> every week and find more things to argue about? Or do you hate meetings
> and wish we only did one a year? :D
Hey again folks. So the response to this was positive, and I've decided
to go ahead and implement it. I unfortunately had to delete and re-
create the calendar.fedoraproject.org entry for the meeting, as
changing its recurrence to every 14 days didn't seem to work properly.
So if you had any kind of subscription for that entry, you'll have to
set it up for the new one - sorry.
I counted the meeting on November 14 as the first meeting in the new
every-other-week era, so the next meeting will be November 28. I will
not send a cancellation mail for November 21st, but I'm sending this
mail to test-announce to make sure folks are aware of the new era :)
I'll also update the wiki page to explain things.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 4 months
2022-11-14 @ 16:00 UTC - Fedora QA Meeting
by Tim Flink
# Fedora Quality Assurance Meeting
# Date: 2022-10-24
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat
Greetings testers!
F37 went GO last week and is due to be released immanently. Let's review any remaining last-minute items for F37 and start looking at F38.
If you have any items for the agenda, please reply to this email to suggest them.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 37 status
3. Fedora 38 changes
4. Test Day / community event status
4. Open floor
1 year, 4 months
2022-11-07 @ **15:00** UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson
# F37 Blocker Review meeting
# Date: 2022-11-07
# Time: **15:00** UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 1 proposed blocker and 1 proposed freeze exception to
review, so let's have a review meeting.
Note that clocks went back in North America this weekend, so the
meeting time is one hour earlier in UTC. If your clocks went back this
weekend, the meeting will be the same time as before in your local
time. If your clocks didn't change, the meeting will be one hour
earlier in your local time.
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 night and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 4 months