Hi, anaconda devs! As one of the follow-ups to the 'eternal blocker
treadmill' discussion, we're going to start with F22 blocker review
this week, and we're going to review proposed blockers for all
milestones at each meeting, instead of only doing Alpha review for
Alpha, Beta review for Beta, Final review for Final. Hopefully this
should mean you (and the other dev teams) have a much earlier handle
on the F22 blocker list.
As always, it will help a lot if someone can be present at the
meeting. As I write this there are 8 proposed blockers for all F22
milestones, so the meeting shouldn't be too long. You can see the
lists here:
https://qa.fedoraproject.org/blockerbugs/milestone/22/alpha/buglist
https://qa.fedoraproject.org/blockerbugs/milestone/22/beta/buglist
https://qa.fedoraproject.org/blockerbugs/milestone/22/final/buglist
and provide input ahead of time as comments on the bugs, of course. We
can make an effort to group the anaconda-related bugs at the start of
the meeting, if someone is willing to come and help review.
In case anyone hadn't spotted my mails/posts about it, we have early
testing up and running for the F22 cycle:
https://www.happyassassin.net/2014/12/24/fedora-22-and-later-nightly-testing/
if all my bits work, I think tomorrow's compose (2015-01-06) should be
the next 'nominated for testing' nightly, as long as boot.iso creation
succeeds, since it will have been 14 days since the last one at that
point.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
--- Begin Message ---
# First F22 Blocker Review meeting
# Date: 2015-01-07
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
While it's not the usual time to start blocker reviews, after much
deliberation at today's QA meeting, it was decided to start the blocker
review process earlier than usual. With that being decided, we're going
to get started this week!
The other change to the blocker review process: we're going to start
going through all the remaining milestones for a release. The thought is
that this will keep bugs from piling up, which gives developers and QA
more time to code and test (respectively). Hopefully this will lessen
the number of really long blocker review meetings.
If we happen to have a bunch of blockers that we can't get through in
one meeting, we'll try to schedule another during the week to get
through them. Currently we have 3 Alpha, 2 Beta and 3 Final proposed
Blockers and 4 proposed Alpha Freeze Exceptions.
If you want to take a look at the proposed or accepted blockers, the full
list can be found here: https://qa.fedoraproject.org/blockerbugs/
Make sure to click through the milestones to see how many we have before
the meeting!
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 F22 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
See you Wednesday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
_______________________________________________
test-announce mailing list
test-announce@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/test-announce
--- End Message ---
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
