Join us on irc.freenode.net in #fedora-meeting for this important
meeting, wherein we shall determine the readiness of the Fedora 25
The meeting is going to be held on Thursday, August 18, 2016 at 17:00
UTC. Please check the [FedoCal] link for your time zone.
Before each public release Development, QA and Release Engineering
meet to determine if the release criteria are met for a particular
release. This meeting is called the Go/No-Go Meeting. Verifying that
the Release criteria are met is the responsibility of the QA Team.
Release Candidate (RC) availability and good QA coverage are
prerequisites for the Go/No-Go meeting. If you have any bug on the
list, please help us with Alpha release. If we won't be ready by
Thursday, we will use this meeting to review blockers and decide what
For more details about this meeting please follow the [GoNoGoMeeting] link.
In the meantime, please keep also an eye on the Fedora 25 Alpha
Blocker list [AlphaBlockers].
Thank you in advance for your support. Regards, Jan
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Hi folks! I'm proposing we cancel Monday's QA meeting. There isn't any
urgent business for that meeting that I'm aware of, we have the blocker
review meeting to discuss F25 Alpha issues, and Go/No-Go for Alpha is
coming up so I'm expecting we'll be focused on F25 Alpha testing. If
you do have something that needs discussing at a meeting, please reply
to this email and we can go ahead and schedule the meeting.
# Fedora Quality Assurance Meeting
# Date: 2016-08-08
# Time: 15:00 UTC
# Location: #fedora-meeting on irc.freenode.net
It's meeting time again tomorrow! We have some more new folks we can
welcome, and we can check in on the new member sponsorship procedure
and the state of F25 Alpha and Test Days.
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 25 Alpha/Test Days status
3. New member welcome, sponsorship, another onboarding meeting?
4. Open floor