Hi folks! I'm proposing we cancel the QA meeting for Monday, as it's a
public holiday in the US, Canada and India, so many folks would be
missing. It would be good to follow up on the btrfs and Xen
discussions, but we can do it the following week I think. Note that
there will be a blocker review meeting, but it will be on *Tuesday*.
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
# F31 Blocker Review meeting
# Date: 2019-09-03
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 4 proposed Beta blockers, 1 proposed Final
blocker and 10 proposed Beta freeze exception to review, so let's have a
Fedora 31 blocker review meeting ON **TUESDAY**! Note, TUESDAY. This is
because Monday is a public holiday in the US, Canada and India, so lots
of folks would be missing for a meeting on Monday, but as we're frozen
for Beta now we shouldn't really skip a week.
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/ .
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 F31 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 Tuesday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Hello testers!
After Flock 2019 this year, it became apparent that there are several folks
who would like to join the testing effort, but do not want to use IRC and
would prefer to communicate over Telegram. Consequently, we have started a
Telegram group that testers can join to communicate with one another!
Please find the link below and add yourself to the group [0].
Note also that the #fedora-qa IRC channel and the Fedora QA Telegram group
have been bridged together, so traffic from one service will appear
seamlessly in the other. This allows current users of IRC to continue to
use their IRC clients as they have been, without missing out on any of the
conversations happening in #fedora-qa, and vice-versa.
Geoff Marr
IRC: coremodule
[0] https://t.me/fedora_qa
Hi all,
Today's an important day on the Fedora 31 schedule[1], with several
significant cut-offs. First of all today is
the Bodhi activation point [2]. That means that from now all Fedora 31
packages must be submitted to
updates-testing and pass the relevant requirements[3] before they will be
marked as 'stable' and moved to the
fedora repository.
Today is also the Beta freeze[4]. This means that only packages which fix
accepted blocker or freeze exception
bugs[5][6] will be marked as 'stable' and included in the Beta composes.
Other builds will remain in updates-
testing until the Beta release is approved, at which point the Beta freeze
is lifted and packages can move to
'stable' as usual until the Final freeze.
Finally, Today is the '100% code complete deadline' Change Checkpoint[5],
meaning that Fedora 31 Changes
must now be code complete, meaning all the code required to enable to the
new change is finished. The level
of code completeness is reflected as tracker bug state ON_QA. The change
does not have to be fully tested
by this deadline'.
Finally, today is also the Software String freeze[7], which means that
strings marked for translation in Fedora-
translated projects should not now be changed for Fedora 31.
Mohan Boddu
[1] https://fedoraproject.org/wiki/Releases/31/Schedule
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
# F31 Blocker Review meeting
# Date: 2019-08-26
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 2 proposed Beta blockers, 1 proposed Final
blocker and 1 proposed Beta freeze exception to review, so let's have a
Fedora 31 blocker review meeting tomorrow!
If you have time today, 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/ .
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 F31 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 day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
Hi folks! I'm proposing we cancel the QA meeting tomorrow, as there
isn't a lot for the agenda. We will be doing a blocker review meeting,
though - I'll send out the announcement for that in a minute.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
Hey folks! I'm proposing we cancel the blocker review meeting for
Monday; there are no proposed blockers and only one boring accepted
blocker on the list.
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
# Fedora Quality Assurance Meeting
# Date: 2019-08-19
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We didn't meet for a few weeks, so let's check in on where we're at.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks. I feel like I had one more topic I just
can't bring to mind right now...if anyone knows what that might have
been, let me know!
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 31 and Rawhide status
3. Process proposals: Xen / EC2 criteria, 'last minute' blockers
4. Storage criteria (drop btrfs? What would that look like?)
5. Test Day / community event status
6. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net