[Test-Announce] 2017-07-03 @ 1600 UTC ** Fedora 26 Blocker Review

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-07-03
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! We're getting close to Final release, and it'd be
good to do a status check on the Accepted Blockers. At this point, we
don't have any more proposals, so it should be a quick meeting. If
you have any time between now and the meeting Monday, please take a
look through the list. It canbe 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 F26 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 tomorrow!
  
[0]  https://fedoraproject.org/wiki/Fedora_Release_Criteria

// Mike
--
Fedora QA

___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-06-26 @ 1600 UTC ** Fedora Blocker Review

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-06-26
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Time for some more blocker review! We got last week off, so we've had a
bit of a backlog show up. Currently there are 7 proposed blockers and
one proposed FE. If you have any time between now and the meeting
Monday, please take a look through the list. It canbe 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 F26 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

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [Test-Announce] Proposal to CANCEL: 2017-06-12 Fedora QA Meeting

[Mike Ruckman]

On Fri, Jun 09, 2017 at 03:23:02PM -0700, Adam Williamson wrote:
> Hi folks! I'm proposing we cancel the QA meeting on Monday. We did a
> pretty good job of checking in this week, and I don't think there's
> anything pressing that needs a meeting this week. The status of Beta is
> a bit of a mess with the remaining libdb issues, but that needs to be
> discussed at a different level than the QA team.
> 
> If anyone does want to have a meeting and is willing to run it, please
> just go ahead and say so (and send out an agenda).
> 
> Mike will be sending out a blocker review meeting announcement for
> Tuesday, I believe.
> -- 
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net

I sent out an email on Friday proposing we cancel the Blocker Review
next week :)

// Mike
--
Fedora QA
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-06-12 @ 1600 UTC ** CANCEL Blocker Review

[Mike Ruckman]

Greetings testers! Since we currently only have one proposed blocker for
Final and we *just* got Beta out the door, I suggest we cancel next
week's blocker review meeting. As always, if you see a reason to have
the meeting on Monday, please reply to the list!

Thanks and have a great weekend!

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-06-05 @ 1600 UTC ** F26 Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-06-05
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of the week again - Blocker Review time! Last week we
were still blocked on the libdb bug (please test! Adam sent an email
with information on it). Currently, that's the only blocker we're
tracking for Beta. However, we have 7 proposed blockers for Final that
we should take a look at. If you have time between now and the meeting
Tuesday, please take a look through the list. It canbe 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 F26 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 rest of the weekend and see you on Monday!
  
[0]  https://fedoraproject.org/wiki/Fedora_Release_Criteria

// Mike
--
Fedora QA


___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-05-30 @ 1600 UTC ** (Tuesday) Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-05-30
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! It's that time again, but because of the US holiday,
we'll be moving the meeting to Tuesday. We have 2 proposed blockers for
Beta and 6 accepted we need to check in on. If you have time between now
and the meeting Tuesday, please take a look through the list. It 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 F26 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

// Mike
--
Fedora QA

___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-05-22 @ 1600 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-05-22
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! We're smack in the middle of Beta Freeze, and we've
got a some bugs to review! Specifically, we have 3/5 Beta Blocker and
Freeze Exceptions to look at. For Final, we have 1 proposed blocker to
review. We'll also take some time to review the Accepted Blockers for
Beta and see how things are progressing. If you have time between now
and the meeting tomorrow, please take a look through the list. It 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 F26 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

// Mike
--
Fedora QA

___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-05-15 ** Blocker Review Proposal to CANCEL

[Mike Ruckman]

Greetings testers! We don't have any proposed blockers for Beta or
Final right now, so I propose that we cancel tomorrows meeting.

If you find a blocker or want to discuss something, please reply to this
thread and we'll have the meeting! 

Thanks!

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-05-08 @ 16:00 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-05-08
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of the week again! We've got 4 proposed blockers for
Beta that we need to look through. If you have time between now and
Monday to go through the list of blockers, please do so. You can
find the full list 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 F26 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

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-05-01 @ 16:00 UTC ** Fedora Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-05-01
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! Last week was a busy week and we had 5 proposed
blockers for Beta and 6 proposed blockers for Final. If you have time 
between now and Monday to go through the list of blockers, please do
so. You can find the full list 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 F26 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

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-04-24 @ 16:00 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-04-24
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! It's that time of the week again: Blocker Review
time! We got a break last week, but now we have a couple to look at -
it should still be a shorter meeting though. We currently have 2
proposals for Beta and 3 for Final. If you have time between now and
Monday to go through the list of blockers, please do so. You can find
the full list 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 F26 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

// Mike
--
Fedora QA

___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-04-17 @ 16:00 UTC ** Proposal to Cancel Blocker Review

[Mike Ruckman]

Greetings testers! I apologize for the late notice (had a holiday
weekend and lost track of time), but I don't see a reason to have a
Blocker Review Meeting tomorrow since we've only 1/1 proposed blockers
for Beta/Final. If you feel strongly that we have the blocker review
tomorrow for those two bugs, please reply to the list!

Thanks and see you on IRC!

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-04-10 @ 1600 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-04-10
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! We've had a chance for a break last week after the
marathon run we had getting Alpha out the door. Great work! Now it's
time to get back into it. We currently have 2 proposals for Beta and 3
for Final. If you have time between now and Monday to go through the 
list of blockers, please do so. You can find the full list 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 F26 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

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-04-03 @ 1600 UTC ** Fedora Blocker Review Proposal to Cancel

[Mike Ruckman]

Greetings testers! We had a long run of blocker reviews the past couple
weeks, and there's currently only one proposal for Beta and one for
Final. I think we can take this week off and focus on finding more
blocker proposals for next week!

Thanks!

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-03-27 @ 1600 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-03-27
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! Apologies for the late notice, but we should
probably have a Blocker Review just to check the status of the existing
Alpha Blockers. Currently, we have 0 proposed and 3 accepted blockers 
for Alpha. We also have 1/3 proposed for Beta/Final. It would be good
to go through the list to ensure we're good to go for Alpha release. So,
if you have time between now and then to go through the list of
blockers, please do so. You can find the full list 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 F26 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

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-03-20 @ 1600 UTC - Blocker Review Meeting

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-03-20
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! Last week we determined that Alpha wasn't ready to
ship, so we've had more time to work on and look for blockers. Currently
we have 1 proposed blocker for both Alpha and Beta, and a whopping 5
proposed for Final. On Monday we'll be getting together to go through
the proposed bugs and determine if they'll block release. You can find
the full list 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 F26 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 Sunday and see you on Monday!
  
[0]  https://fedoraproject.org/wiki/Fedora_Release_Criteria

// Mike
--
Fedora QA
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2017-03-13 @ 1700 UTC - Fedora 26 Blocker Review

[Mike Ruckman]

# F26 Blocker Review meeting
# Date: 2017-03-13
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! We're getting ready to make a Go/No-Go decision for
F26 Alpha and we've got 3 proposed blockers for Alpha. Beta and Final
each have 1. We should have a blocker review meeting so we can get
ready for the Go/No-Go meeting on Thursday. If you have some time this
weekend, take a quick look at the proposed blockers. You can find the
full list 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 F26 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
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2015-10-26 @ 1600 ** Fedora 23 Blocker Review

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-10-26
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It looks like we get to have at least one more F23 blocker review
meeting before release (isn't that exciting!?). We have 2 newly proposed
blockers to look at, and several accepted blockers to keep tabs on
before the next Go/No-Go on Thursday.

If you have time this weekend, to take a look at the proposed or
accepted blockers before the meeting -  the full list 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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria


-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-10-19 @ 16:00 UTC ** Fedora 23 Blocker Review

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-10-19
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Last week we did an out-of-sync blocker review because bugs were
stacking up and Go/No-Go is coming up. Even though we cleaned out the
list, we're already back up to 6 proposed blockers and 7 proposed FEs.
Needless to say, we'll be having our usual blocker review meeting
tomorrow.

If you have time tonight or tomorrow, to take a look at the proposed or
accepted blockers before the meeting -  the full list 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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria


-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-10-05 @ 1600 UTC ** F23 Blocker Review Meeting

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-10-05
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of the week again: blocker review time! There's currently
11 proposed blockers we need to look through. We'll be meeting at our
usual time and location.

If you have time today, to take a look at the proposed or accepted
blockers before the meeting -  the full list 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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Log Data Retention

[Mike Ruckman]

On Mon, Sep 28, 2015 at 12:24:12PM -0600, Tim Flink wrote:
> On Mon, 28 Sep 2015 12:20:03 -0600
> Tim Flink  wrote:
> 
> I wonder if this ends up being the email list equivalent of talking to
> myself :)
> 
> It just seemed like a cleaner way to separate my answers from the
> questions
> 
> 
> > The questions raised so far are:
> > 
> > 1. How long is long enough to keep log and execution data?
> 
> 6-12 months should be more than enough but it might be worth trying
> to keep a release-lifetime of logs (~18 months, including pre-release)
> 

I would think we keep log/execution data for current milestone-1, so if
we're in Beta, we keep Beta and Alpha logs. It's not very common that
something breaks in Final and we need to look all the way back to Alpha,
is it? As for packages not in the frozen set, I'd think 60-90 days would
be enough.

> > 2. Should be be cleaning up anything that references builds/artifacts 
> > (like links in resultsdb) before we delete them?
> 
> Ideally, yes but I don't think it's worth more than a day's effort
> for one person if we have proper 404 processing on the machine hosting
> the artifacts.
> 
> If it does become an issue in the future, it wouldn't be difficult to
> go back and change dead links if we needed to.
> 

That makes sense to me.

> > 3. Do we want to put resources into figuring out whether the result
> > was a PASS or FAIL before deleting it?
> 
> No, it's not worth the effort - I'd rather just store more logs than
> put much dev time into deciding which logs to delete
> 
> > 4. Should fesco be involved in this decision?
> 
> Either way - I suspect that they're not going to have much of an
> opinion and it adds bureaucracy to the process but I suppose that the
> decision would be a bit more "official" if we asked them.

I don't know that we need fesco for this decision, but it might be a
good thing to make sure is documented somewhere should someone ask.

> 
> Tim

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

[Test-Announce] 2015-09-28 @ 1600 UTC ** Fedora Blocker Review

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-09-28
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time again: Blocker review time! We currently have 4 proposed
blockers for Final. It'd be good to meet and knock them out. Should be
a short meeting.

If you have time this weekend, to take a look at the proposed or accepted
blockers before the meeting -  the full list 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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-09-21 @ 1600 UTC ** [Moved] F23 Blocker Review

[Mike Ruckman]

Well, it appears that Bugzilla is currently experiencing some issues, so
we had to move today's blocker review to tomorrow. Providing that
Bugzilla is up and working by 1600 UTC tomorrow (2015-09-22), we'll be
having the blocker review then.

Thanks!

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-09-21 @ 1600 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-09-21
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

We're getting down to the final stretch for Fedora 23 with the Beta
release happening this Tuesday. Great work! To make sure we stay on
schedule, we'll be having a blocker review meeting to go over the
4 Final proposals we have. Should be a short meeting.

If you have time tomorrow, to take a look at the proposed or accepted
blockers before the meeting -  the full list 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 F23 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 tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-09-14 @ 1600 UTC ** F23 Blocker Review Meeting

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-09-14
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Earlier this week we knocked out a bunch of blocker proposals, and come
Monday we'll need to do the same. Luckily though, there's currently only
1/1 proposed blocker for Beta/Final. Also, with freeze in effect, we'll
need to take a look at those as well.

If you have time this weekend, to take a look at the proposed or accepted
blockers before the meeting -  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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-09-07 @ 1600 UTC ** Proposal to CANCEL: Blocker Review

[Mike Ruckman]

With this coming Monday being a US holiday, I propose that we cancel the
Blocker review meeting. We're currently sitting at 3/1 proposals for
Beta and Final - so I don't think it'll put us too far behind.

Of course, if someone else wants to run the meeting in my stead, that's
also fine. Otherwise, enjoy having your Monday morning back!

Thanks!

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Resources for upstream testing?

[Mike Ruckman]

On Tue, Sep 01, 2015 at 10:52:42PM -0700, Dave Johansen wrote:
> I'm working on packaging hgsubversion (
> https://bugzilla.redhat.com/show_bug.cgi?id=1221459 ) and I've run into an
> issue where some of the tests pass on F22 and F23 but fail on Rawhide. I've
> done some simple debugging, but it would be much easier if upstream could
> do some testing on their own (
> https://groups.google.com/d/msg/hgsubversion/q47xvqDDmS0/Mk29v2voFAAJ ).
> Are there any machines or docker images that upstream could use to debug
> the issue without having to create a Fedora account, install Fedora or jump
> through any hoops like that?
> Thanks,
> Dave

Dave,

We do have docker images that can be used [0] - but we currently don't
have a user friendly way to find them. You currently have to look
through koji to find them [1].

Hope this helps!

[0]
https://kojipkgs.fedoraproject.org//work/tasks/7896/10927896/Fedora-Docker-Base-rawhide-20150902.x86_64.tar.xz
[1]
http://koji.fedoraproject.org/koji/tasks?start=0=all=tree=image=-id

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-08-31 @ 1600 UTC ** Fedora 23 Blocker Review

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-08-31
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of week again - Blocker Review! This time around we have
1/3 proposed blockers for Beta/Final. We'll meet up at our regular time
after the QA meeting to go through them. It'll likely be a short
meeting.

If you have time tomorrow, to take a look at the proposed or accepted
blockers before the meeting -  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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-08-24 @ 1600 UTC ** F23 Blocker Review Meeting

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-08-24
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

This week we had an out of band blocker review where we plowed through
a bunch of proposals. Next week we'll be having another meeting (at
the usual day and time) to finish the rest off. We currently have 1/1
proposals for Beta/Final - so it should be a shorter meeting.

If you have time this weekend, to take a look at the proposed or accepted
blockers before the meeting -  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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Rescheduling this weeks Blocker review meeting

[Mike Ruckman]

Hey all,

It seems the lack of sleep from Flock caught up with me Sunday night and I 
didn't wake up in time
to run the blocker review scheduled for Monday morning. We currently have 6/7 
proposed blockers
for Beta and Final, so I think it will still be good to have a Blocker review 
this week. Does
this Thursday (2015-08-20) at 16:00 UTC work for people? If there's a better 
time, please
respond to the test list and we can find a better window to run the review.

Thanks!

Mike Ruckman
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-08-10 @ 1600 UTC ** PROPOSAL TO CANCEL Fedora 23 Blocker Review

[Mike Ruckman]

With the recent decision to ship Alpha, Flock being next week and people
traveling, I propose that we cancel the next Blocker Review meeting.
Currently there are 2/4 proposals for Beta/Final - so if someone wants
to run the meeting, go for it. Otherwise, enjoy your blocker review free
time :)

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-08-03 @ 1600 UTC ** F23 Blocker Review

[Mike Ruckman]

# F23 Blocker Review meeting
# Date: 2015-08-03
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hey, look at me sending out an announcement this time! Next week we only
have a couple proposed blockers to go through: 1/2/1 (Alpha/Beta/Final).
Also, we have 5 proposed FEs to look at for Alpha. Take some time over
the weekend to check out the proposals if you get a chance - it'll help
us get finished quickly.

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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-07-13 @ 1600 ** Fedora 23 Blocker Review

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-07-13
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

With branch almost here (this Tuesday), and freeze a couple weeks after
that (2015-07-28), I think it's time we started getting back into
regular blocker review meetings. This week we only have 2 blockers to
look at, so it should be a short meeting.

If you have time tomorrow, to take a look at the proposed or accepted
blockers before the meeting -  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 F23 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria


-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Proposal to Cancel: 2015-07-06 Fedora Blocker Review

[Mike Ruckman]

Greetings fellow testers!

As we only have one blocker proposed, [0] I propose we cancel tomorrow's
blocker review meeting. Everyone can vote in ticket as their time allows.
If someone thinks it'd be better to have the meeting, please ping in IRC
and we'll go ahead and have the meeting.

Thanks!

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1236937

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Call for Fedora 23 Test Days

[Mike Ruckman]

F23 is about to branch [0] and it's time we started thinking about what
we'd want to have a test day for. There are several changes accepted
already for F23, and more that have yet to be decided [1]. You can find
the list here:

http://fedoraproject.org/wiki/Releases/23/ChangeSet

Please take some time and look through the list and see if there's
anything you'd be interested in testing - or if there's something you
think should get some testing that isn't in the ChangeSet!

For those of you not familiar with test days, a test day is an
online event aimed at testing a specific feature of an upcoming Fedora
Release. By utilizing IRC for organization/coordination and a Wiki
page for instructions and results, test days are easy to organize.
Anyone can request to host a test day or request that the QA team help
you out with the organization of the test day. A test day can be ran
for any feature or area of a distribution that focused testing would be
useful for. More information on test days can be found here:
https://fedoraproject.org/wiki/QA/Test_Days .

To propose a test day, file a ticket on the QA Trac. A full
explanation can be found here:
https://fedoraproject.org/wiki/QA/Test_Days/Create . The SOP for
hosting a test day is here:
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management . 

Traditionally test days have been held on Thursdays, but if you'd prefer
to have it on another day that's fine too. We're pretty flexible, but
having plenty of lead time helps to get the word out. Just put in your
ticket the date or time-frame you'd like, and we'll figure it out from
there.

If you have any questions about test days or the process, please don't
hesitate to contact me or any other QA Team member in #fedora-qa on
Freenode or respond on the test list.

Thanks and happy testing!

[0] https://fedoraproject.org/wiki/Releases/23/Schedule
[1] https://fedorahosted.org/fesco/ticket/1445

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Self-Introduction: Mike Ruckman (roshi)

[Mike Ruckman]

Hey devel list!

I'm Mike (mostly known as roshi on freenode) and I'd like to become a
packager. I don't have much experience (outside of local scratch builds
to test fixes) with packaging, but I'd like to learn more and get
involved. I've posted my first package for review [0] for a tool called
testcloud. testcloud makes it easy to locally boot and test cloud images
and is currently being used for the disposable clients for taskotron.
Any feedback or patches welcome!

Thanks!

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1234649

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Fedora 22 Final Release Candidate 2 (RC2) Available Now!

[Mike Ruckman]

As per the Fedora 22 schedule [1], Fedora 22 Final Release Candidate 2 
(RC2) is now available for testing.

Content information, including changes, can be found at
https://fedorahosted.org/rel-eng/ticket/6166#comment:12. Please see 
the following pages for download links and testing instructions. 
Normally dl.fedoraproject.org should provide the fastest download, but 
download-ib01.fedoraproject.org is available as a mirror (with an 
approximately 1 hour lag) in case of trouble. To use it, just replace 
dl with download-ib01 in the download URL.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Workstation and Desktop:

https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test

Server:

https://fedoraproject.org/wiki/Test_Results:Current_Server_Test

Cloud:

https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

Summary:

https://fedoraproject.org/wiki/Test_Results:Current_Summary

All Final priority test cases for each of these test pages [2] must  
pass in order to meet the Final Release Criteria [3]. Help is available 
on #fedora-qa on irc.freenode.net [4], or on the test list [5].

Create Fedora 22 Final test compose (TC) and release candidate (RC)  
https://fedorahosted.org/rel-eng/ticket/6166

Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current

[1]  http://fedorapeople.org/groups/schedule/f-22/f-22-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
[4] irc://irc.freenode.net/fedora-qa
[5] https://admin.fedoraproject.org/mailman/listinfo/test

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-04-06 @ 1600 UTC ** F22 Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-04-06
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! Tomorrow we'll be having another blocker review
directly after the QA meeting. Currently we have 7 proposed blockers for
Beta and none proposed for Final. 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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-03-30 @ 1600 UTC ** Fedora 22 Blocker Review

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-03-30
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Well, this email is going out a bit late, but I'm sure you all know it's
that time of the week again! We've had a few more proposals since our
meeting last week. We currently have 5 beta and 2 final proposals to
review.

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 tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-03-16 @ 1600 UTC ** Fedora Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-03-16
# Time: 1600 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's coming up to that time of the week again: Blocker Review! Currently
we have 5/1 proposed blockers for Beta and Final. Again, we're meeting
at 1600 UTC right after the QA meeting. If you have some time this
weekend, take a look at the bugs. Or, if you won't be able to make it to
the review, go ahead and vote in the comments. 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

Have a good weekend and see you Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-03-02 @ 1700 UTC ** Fedora 22 Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-03-02
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Another week and a couple TCs later, it's time for some blocker review
goodness! Also, as an added bonus, Alpha Freeze is upon us so we get to
look over FE bugs as well. Currently we have 8/1/0 for blockers and
10/0/0 FE's to look at. It'll likely be a longer meeting than what we've
grown accustomed to, so take some time this weekend to check out the
proposals (you can even vote in the bug comments if you like).

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/

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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-02-23 @ 1700 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-02-23
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of the week again! After another week of testing we
have 4 proposed Alpha blockers and 2 proposed for final.

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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-02-16 @ 1700 UTC ** Fedora Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-02-16
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's Blocker Review time again! While we don't yet have an Alpha TC to
test, testing against rawhide has continued. The results have yielded a
couple proposed blockers: 3 Alpha and 2 Final. 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

Have a good weekend and see you Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-02-09 @ 1700 UTC ** F22 Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-02-09
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

So far this week we've found 1 proposed Alpha blocker as well as 5
proposed for Final. 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

Have a good weekend and see you Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Call for Fedora 22 Test Days

[Mike Ruckman]

Another testing cycle is finally upon us, and it's about time we got
some Test Days scheduled for the F22 cycle. The Anaconda team has
already requested a test day [0] and there are several other changes
coming to F22 that could use some testing love - a full list can be
found here:

  http://fedoraproject.org/wiki/Releases/22/ChangeSet

F22 also has several self-contained changes that could use some testing.
So my thought was, if there were things people would like to get tested,
but didn't think it warranted an entire day - then we could group these
together and run a test day to poke at several different things at the
same time. Thoughts on this?

For those of you not familiar with test days, a test day is an
online event aimed at testing a specific feature of an upcoming Fedora
Release. By utilizing IRC for organization/coordination and a Wiki
page for instructions and results, test days are easy to organize.
Anyone can request to host a test day or request that the QA team help
you out with the organization of the test day. A test day can be ran
for any feature or area of a distribution that focused testing would be
useful for. More information on test days can be found here:
https://fedoraproject.org/wiki/QA/Test_Days .

To propose a test day, file a ticket on the QA Trac. A full
explanation can be found here:
https://fedoraproject.org/wiki/QA/Test_Days/Create . The SOP for
hosting a test day is here:
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management . 

Traditionally test days have been held on Thursdays, but if you'd prefer
to have it on another day that's fine too. We're pretty flexible, but
having plenty of lead time helps to get the word out. Just put in your
ticket the date or time-frame you'd like, and we'll figure it out from
there.

If you have any questions about test days or the process, please don't
hesitate to contact me or any other QA Team member in #fedora-qa on
Freenode or respond on the test list.

Thanks and happy testing!

[0] https://fedorahosted.org/fedora-qa/ticket/457

--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-02-02 @ 1700 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-02-02
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of week again, time for some Blocker Review! Currently we
have 1 Alpha and 1 Beta blocker proposed - so it should be a short
meeting. We'll be sticking with the new trend of going through all the
milestones during this meeting.

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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-01-26 @ 1700 UTC ** F22 Blocker Review Meeting

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-01-26
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

I seem to have forgotten how to use the send button on my mail client,
so this annoucnement is getting out a bit late. Apologies for that!
We've got another blocker review in a couple hours! We currently have
several proposed blockers: 2 Alpha, 1 Beta and 2 Final. So if you're
around after the QA meeting, come and join us for some blocker review
goodness :)

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 soon!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-01-12 @ 1700 UTC ** Fedora Blocker Review **NEW TIME**

[Mike Ruckman]

# F22 Blocker Review meeting
# Date: 2015-01-12
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of week again, time for some Blocker Review! While it
might seem like I've lost track of what day it is again (which happens,
I admit), we discussed it this week and decided to give Mondays after
the QA meeting a try for the blocker review. So, this Monday we'll be
having the review at 1700 UTC instead of the normal Wednesday time.

We'll be sticking with the new trend of going through all the milestones
during this meeting. Currently, accross all the milestones, we have 3
proposed blockers. Hopefully it'll be a short meeting.

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 Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2015-01-07 @ 1600 UTC ** Fedora 22 Blocker Review Meeting

[Mike Ruckman]

# 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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-12-03 @ 1600 UTC ** Conditional Blocker Review Meeting

[Mike Ruckman]

Greetings testers! Typically we'd have a blocker review meeting
tomorrow, but with Go/No-Go this Thursday and a pretty solid RC out and
being tested, we might not need one. Currently there are no proposed
blockers (and let's hope we've handled all of them), so we won't be
having a meeting.

OTOH, if we do find some tonight or before the meeting tomorrow we'll go
ahead and have the meeting to discuss whatever has been found.

Just wanted to give everyone a heads up. Thanks!

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-11-26 @ 1600 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-11-26
# Time: 16:00 UTC (run date -d '2014-11-26 16:00 UTC' to see local time)
# Location: #fedora-blocker-review on irc.freenode.net

While we just had a out of band blocker review today after the QA meeting, we'll
still be having our regularly scheduled blocker review this Wednesday. We
managed to knock out all of the blockers and FEs this morning, but still we
had 2 proposed blockers and 1 proposed FE since.

I would get ready for more proposals before the meeting on Wednesday, but if we
don't get any it should be a short meeting. Maybe this time around we can all
watch the FEsCo meeting :)

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist

We'll be evaluating these bugs to see if they violate the Final
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Fedora Atomic Test Day

[Mike Ruckman]

Greetings, all!

Tomorrow (or today for those of you not in North America) will be the first
Atomic Testday! The Fedora Atomic host is a new image designed to securely and
easily run Docker containers - all based on Project Atomic [0]. Because it's
new ground, testing is required for a successful release.

The Atomic image utilizes rpm-ostree [1] to allow you to update and revert your
installed package set just like a Git repo. This allows for easy upgrades and
an easy method of reverting back to a known good state should something go
wrong after an update.

Come join us for a day of testing and exploration into all Atomic offers for
running your containerized applications. Information on the testday can be
found on the Wiki [2] or drop by the #fedora-test-day channel on Freenode if
you have any questions.

See you tomorrow (or later today)!

[0] http://projectatomic.io
[1] https://github.com/projectatomic/rpm-ostree
[2] https://fedoraproject.org/wiki/Test_Day:2014-11-20_Atomic

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-11-19 @ 1600 UTC ** Blocker Review Meeting

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-11-19
# Time: 16:00 UTC (run date -d '2014-11-19 16:00 UTC' to see local time)
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of the week again! Things have been moving along smoothly after
the Beta release - and now Freeze is upon us for final. This means we'll not
only be giving some love to the proposed blockers, but also looking into the
proposed Freeze Exceptions. Currently we have 6 proposed blockers and 5
proposed FEs.

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist

We'll be evaluating these bugs to see if they violate the Final
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-11-12 @ 1600 UTC ** Fedora Blocker Review Meeting

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-11-12
# Time: 16:00 UTC (11:00 EST, 08:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of the week again! Last week we had 15 proposed blockers, which
we managed to get down to 4 or so. This week we have 11 to go through. Also,
we're keeping the meeting time locked into UTC so make sure to check your local
time (for those of us who had a time change recently).

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist

We'll be evaluating these bugs to see if they violate the Final
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Server Test Day Tomorrow (2014-11-07)

[Mike Ruckman]

Greetings Testers!

Tomorrow we'll be holding a testday for the Server product. Along with general
testing there will be a focus on freeIPA, openLMI, cockpit and Rolekit. If you
have some time, or want to get more familiar with all the new features Server
brings, drop by the #fedora-test-day channel on freenode and run some tests,
we'd love to see you there! More information can be found on the wiki [0].

Thanks!

[0] https://fedoraproject.org/wiki/Test_Day:2014-11-07_Server

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-11-05 @ 1600 UTC ** F21 Blocker Review

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-11-05
# Time: 16:00 UTC (11:00 EST, 08:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net

The first TC of Final is upon us! Along with that, we've changed up the release
schedule a bit so we need to get to finding and knocking out these blocker bugs
for Final. Currently we have 15 proposed blockers and 3 proposed FEs to get
through.

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist

We'll be evaluating these bugs to see if they violate the Final
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-10-22 @ 1600 UTC ** Fedora 21 Blocker Review Meeting

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-10-22
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

We've already had one blocker review meeting this week (which is likely 
why I forgot to send this email until now), but it's time for another!
With Go/No-Go being decided tomorrow we have plenty to do in order to be
ready. So far we've got 9 proposed blockers and and 4 proposed freeze 
exceptions to look through for this meeting. 

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist

We'll be evaluating these bugs to see if they violate the Beta
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 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 in a couple hours!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-10-15 @ 16:00 UTC ** F21 Blocker Review Meeting

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-10-15
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

As testing of Beta TC3 continues, it's time for another blocker review meeting.
Currently we have 3 proposed blockers and 2 proposed FEs. We have 10 accepted
blockers to review. Should be a shorter meeting :)

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist

We'll be evaluating these bugs to see if they violate the Beta
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Installer - how to get a shell ?

[Mike Ruckman]

On Wed, Oct 08, 2014 at 08:12:29AM +1100, David Timms wrote:
 Hi, booted up a F21 alpha iso cd, and realized after the long wait that
 I didn't have networking configured during boot, and this probably led to:
 - no repository
 - no package selection possible.
 
 I thought I would Alt-F1,F2 etc to find the shell (and set up networking
 manually, rather than waiting for a second boot cycle).
 F1 had the list of ttys along the bottom, but the shell one (F2 from
 memory) accepts enter (which outputs a blank line, but never gave a
 prompt or other response.
 
 What's the trick to getting that (usable) shell to do things like
 check/set network ?
 
 Also, should we be able to access wireless network during the first part
 of the installer (for network download/install of repos/packages) ?

The list of ttys you see along the bottom is from tmux [0]. From that screen
if you were to hit `ctrl-b 2` it would switch to the pane labelled 'shell' at
the bottom of the screen.

I use tmux everyday - it's pretty awesome :)

[0] http://tmux.sourceforge.net/

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-10-03 @ 16:00 UTC ** Out of band Blocker Review Meeting

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-10-03
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Towards the end of today's blocker review meeting, we decided it would be good
for us to have a another meeting this week to deal with the unusually large 
number of blockers left we have to go through. Currently the number we still 
have is 15. So if you're available to help go through the list this Friday,
we'd appreciate the help going through the list.

On the other hand, if it works out for more people to do the meeting tomorrow,
we can do that as well. I just feared it would be too short of notice to go
ahead and schedule for tomorrow. Reply to t...@lists.fedoraproject.org or ping
me on IRC if tomorrow works better for you, we can adjust accordingly if there
is enough interest.

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist

We'll be evaluating these bugs to see if they violate the Beta
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that
should be sorted quickly.

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 Friday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-10-01 @ 16:00 UTC ** Fedora Blocker Review Meeting

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-10-01
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
 
It's that time of the week again! Currently there are 14 bugs that need some
TLC. Happily, that's 11 less than there were last week, so we might stand a 
chance of getting through them all in the allotted time.

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist

We'll be evaluating these bugs to see if they violate the Beta
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that  
should be sorted quickly.

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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-09-24 @ 16:00 UTC ** F21 Blocker Review

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-09-24
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
 
Well now that we've finally kicked Alpha out the door, it's time to do some 
Beta blocker review. You might think, Oh, hey - that'll be easy, we just 
started! However, you'd be wrong. We've been tracking beta and final blockers
as well this whole time :) With that said, we have a total of 25 proposed
blockers to go through. So be prepared to get comfortable for the meeting.

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist

We'll be evaluating these bugs to see if they violate the Beta
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that  
should be sorted quickly.

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 tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-09-17 @ ** 16:00 UTC ** - F21 Blocker Review

[Mike Ruckman]

# F21 Blocker Review meeting 
# Date: 2014-09-17
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Greeting testers! Tomorrow we've got another Blocker Review to do.
As of today there are no proposed blockers and 6 proposed FEs for F21 Alpha. 
The full list can be found here:
https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist

We'll be evaluating these bugs to see if they violate the Alpha
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that
should be sorted quickly.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-09-10 @ 16:00 UTC ** F21 Blocker Review

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-09-10
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
 
It's everyones favorite time of the week! Our next blocker review meeting will
be this Wednesday (as usual). As of right now, we have 2 proposed blockers and
4 proposed freeze exceptions. Hopefully this week we have a good turnout and 
finish these up quickly :)

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist

We'll be evaluating these bugs to see if they violate the Alpha
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that  
should be sorted quickly.

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-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-08-27 @ 16:00 UTC ** F21 Blocker Review

[Mike Ruckman]

# F21 Blocker Review meeting
# Date: 2014-08-27
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Greetings testers! It's time again tomorrow for another blocker review meeting!
Currently there are 4 proposed blockers, but more can certainly be reported
before the meeting.

If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist

We'll be evaluating these bugs to see if they violate the Alpha
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that
should be sorted quickly.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-08-06 @ 16:00 UTC ** F21 Blocker Review #5

[Mike Ruckman]

# F21 Blocker Review meeting #5
# Date: 2014-08-06
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

It's that time of the week again - more blocker review goodness. With flock
going on, I don't know if there will be enough people to have a meeting - 
but that's OK because as of today we only have a single proposed blocker and 
a single proposed FE. This meeting will likely be just for checking on the 
status of our accepted blockers and ensure that they're being worked on.

If you want to take a look at the accepted blockers, the full list can be found 
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist

We'll be evaluating these bugs to see if they violate the Alpha
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that
should be sorted quickly.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria


-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-08-04 @ 15:00 UTC - Fedora QA Meeting

[Mike Ruckman]

# Fedora Quality Assurance Meeting
# Date: 2014-08-04
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's time again for another QA meeting tomorrow! With Flock and the F21 
TC being delayed it's going to be a short meeting. I've simply stolen 
agenda items from the email Adam sent earlier - if you have anything to 
add feel free to bring it up in the meeting!

== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 21 status
3. Nightly Install Testing
4. Open floor

// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-07-30 @ ** 16:00 UTC ** - F21 Blocker Review #4

[Mike Ruckman]

# F21 Blocker Review meeting #4
# Date: 2014-07-30
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

We've got another blocker meeting coming up this week. As of today
there are 2 proposed blockers and 1 proposed FE for F21 Alpha (same as
last week). The full list can be found here:
https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist

We'll be evaluating these bugs to see if they violate the Alpha
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that
should be sorted quickly.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-07-23 @ ** 16:00 UTC ** - F21 Blocker Review #3

[Mike Ruckman]

# F21 Blocker Review meeting #3
# Date: 2014-07-23
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

We've got another blocker meeting coming up this week. As of today
there are 2 proposed blockers and 1 proposed FE for F21 Alpha (so it
should be a shorter meeting). The full list can be found here:
https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist

We'll be evaluating these bugs to see if they violate the Alpha
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that
should be sorted quickly.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

==
// Mike
Fedora QA
irc: roshi | twitter: roshi_fedora 
blog: roshi.fedorapeople.org 


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-07-16 @ ** 16:00 UTC ** - F21 Blocker Review #2

[Mike Ruckman]

# F21 Blocker Review meeting #2
# Date: 2014-07-16
# Time: 16:00 UTC (12:00 EST, 09:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net

It's blocker review time again! Now that we're rolling along with the
F21 alpha release process we're moving back to regular blocker
review meetings. As of today there are 2 proposed blockers and 1
proposed FE for F21 Alpha. The full list can be found here:
https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist

We'll be evaluating these bugs to see if they violate the Alpha
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0]. Product specific plans are still being solidified, but that
should be sorted quickly.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria

==
// Mike
Fedora QA
irc: roshi | twitter: roshi_fedora 
blog: roshi.fedorapeople.org


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2014-06-30 @ 15:00 UTC - Fedora QA Meeting

[Mike Ruckman]

# Fedora Quality Assurance Meeting
# Date: 2014-06-30
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location:
#fedora-meeting on irc.freenode.net

Greetings testers!

This is a reminder of the upcoming QA meeting.  Please reply to this
mail with any suggestions for additions to the agenda.

The current proposed agenda is included below.  If no topics beyond the
standard Previous meeting follow-up and Open Discussion topics are
present or proposed, the meeting will be cancelled.

== Proposed Agenda Topics ==
1.  Fedora 21 Status Updates
 A.  Blocker Status - Count and Any especially worrysome ones?
 B.  roshi and/or pschindl report on Test Days - See Action Item
from 2014-06-09 meeting notes
 C.  Rawhide Testing Status

2.   Taskotron Discussion
 A.  Status Report
 B.  bodhi2 integration discussion?

3.   Alpha Release Related Items ??

4.   Open Floor


Anyone with additional agenda items please respond to the mailing list
this weekend.  If you hit send after 0400 Monday they probably won't
make the meeting and you'll have to raise them during Open Floor.

Sincerely,
Mike Ruckman


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Tools, Borrowing Code and libtaskotron's License

[Mike Ruckman]

On Mon, 12 May 2014 22:00:33 -0600
Tim Flink tfl...@redhat.com wrote:

 One of the things that I've wanted for taskotron is to keep the
 directive documentation inside the code for those directives - similar
 to how ansible does their documentation for modules [1].
 
 [1] http://docs.ansible.com/modules_by_category.html
 
 Mike has been working on some code to make that happen [2] (be nice if
 you review - I asked him to cut as many corners as possible for the
 moment) that borrows heavily from ansible since the approaches have
 quite a bit of overlap. The potential issue here is license
 incompatibility - libtaskotron (and all of the other qa devel
 projects) are gpl2+ and ansible is gpl3. If we take code from
 ansible, we'll have to re-license libtaskotron as gpl3.
 
 [2] https://phab.qadevel.cloud.fedoraproject.org/D93
 
 I'm not against doing this in principle but putting my license
 pedant hat on for a moment, I don't think it'll be quite as simple
 as changing some text files.
 
   - I'm not 100% clear on whether gpl3 code can use gpl2 libraries.
 I'm under the impression that there is generally accepted leeway here
 in the case of dynamic languages like Python but I want to run
 this past FPC or Fedora legal first.
 
   - If gpl3 code can't use gpl2 libraries, we need to do a code audit
 to verify that we aren't using anything that's strictly gpl2 only.
 I did a quick check of libtaskotron and I think we're OK here but
 I haven't checked everything else.
 
   - Are we OK with saying anything run by libtaskotron has to be gpl3
 compatible? This gets into another area that I'm personally fuzzy
 on (the line between derivative and usage) but I don't know of any
 gpl2-only or agpl libraries that we'd want to use with
 libtaskotron so this may end up being a non-issue entirely
 
   - This could cause problems if we share code between our other qa
 projects since they're all gpl2+. On the other hand, all
 contributions are gpl2+ so we can just re-license them as needed,
 assuming that they don't link to anything that's strictly gpl2.
 
 If we decide not to use the code in [2], we have 2 options for
 documentation:
 
   - completely re-implement the doc-building code in a way that avoids
 the license issue
   - find another way to do the directive documentation.
 
 I'd appreciate thoughts on the issues here. I'm leaning towards
 re-license as gpl3 and take the code from ansible but I could be
 missing some complication here.
 
 Tim

I'm not terribly familiar with the nuances of software licensing, but I
don't see a ton of reason to not re-license to gpl3 _aside_ from the
potential to not be able to use strictly gpl2 code in the future. The
code in question isn't terribly difficult to write from scratch - but in
the future we might need something that's gpl2 that *is* hard to write
from scratch.

That would be my only worry when it comes to re-licensing the whole
project for essentially one script.

// Mike


signature.asc
Description: PGP signature
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Re: Taskotron and Cloud Image tests

[Mike Ruckman]

On Mon, 14 Apr 2014 17:01:49 +0200
Vitaly Kuznetsov vi...@redhat.com wrote:

 Vitaly Kuznetsov vi...@redhat.com writes:
 
  Hi Tim  all,
snip
 
  Yesterday I've tried setting up Taskotron (according to
  http://roshi.fedorapeople.org/dexy-themed/) on 3 F20 VMs in EC2 and
  actually I've failed (some ansible playbooks are out-of-sync with
  some git repos, e.g. 'master playbook' is failing with 'stderr: cp:
  cannot stat '/home/qaadmin/trigger/jobtrigger.py': No such file or
  directory' in 'TASK: [copy fedmsg config]'. I totally understand
  these instructions and repos are rather proof-of-concept and can be
  slightly outdated but I want to ask about 'minimalistic one-host
  dev environment' setup anyway. Can 'Host' be eliminated from the
  setup completely and can we merge Master and Slave (in case we'll
  need it for 'cloud') on one host? That would help a lot.
 
  I'm looking forward to hearing from you.
 
 Sorry to bug you again about this, am I completely out of sync with
 whatever is going on? I would really appreciate your comments..
 

Hey Vitaly,

That tutorial I wrote is pretty out of date since most of the ansible
playbooks have been heavily refactored. One of the things I'm going to
be working on is updating the tutorial to reflect the changes. As for
removing 'Host' from the setup - that could be done (AIUI, but I don't
know what the value add would be. Tim would be in a better position to
answer about consolidation between Host, Master and Slave.

// Mike


signature.asc
Description: PGP signature
___
qa-devel mailing list
qa-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Re: Default invocation of pytest for qadevel projects

[Mike Ruckman]

On Thu, 6 Mar 2014 07:29:32 -0700
Tim Flink tfl...@redhat.com wrote:

 On Thu, 6 Mar 2014 05:44:15 -0500 (EST)
 Kamil Paral kpa...@redhat.com wrote:
 
   For the qadevel projects I'm aware of, we've been using pytest for
   our unit/functional test runner.
   
   As part of the shared configuration, tests are split up into two
   categories, unit and functional. Unit tests are fast, do not touch
   the network, database or filesystem (there are some exceptions to
   that last part, though). Functional tests tend to be more
   integration tests that can set up a database or do other actions
   which fall outside of the previous definition of unit test.
   
   When you run pytest without any extra args, only the unit tests
   are run. The '--functional' arg is needed to enable collection and
   execution of the functional tests.
   
   Kamil recently made a request [1] to do one of two things:
   
   [1] https://phab.qadevel.cloud.fedoraproject.org/T89
   
   1. Change the default such that functional tests are collected and
   exclude them from collection using a '--unit' arg
   
   2. Change the functional arg from '--functional' to something
   shorter, like '--func'
   
 * note that there are restrictions on which args we can use. For
   example, '-f' is not allowed as single letter args are
   reserved for pytest itself
   
   As stated in T89, I don't have a strong opinion on this as long as
   it's possible to exclude the functional tests from collection and
   we make the same change across all of our active projects.
   However, I wanted to put this up for a wider discussion before
   changing things.
   
   Any other thoughts on this proposed change?
  
  I should remember to read the mailing list before the Phab comments.
  I already closed the task as wontfix with my comment included:
  https://phab.qadevel.cloud.fedoraproject.org/T89#9
  
  I agree that you have a point in running just the unit tests by
  default.
 
 For my workflow, sure. On the other hand, I'm not sure what other
 peoples' workflow looks like and if it reduces confusion, we may be
 better off changing the defaults to run functional tests. As I stated
 in the ticket, as long as I can turn off the functional tests with a
 command line arg, my workflow won't be affected.
 
 Other thoughts on which is a better default?
 
  Changing --functional to --func would be nice, though. It
  even matches the file prefix for func tests, 'functest_'.
 
 Sure, I'm game for changing that. The two args that come to mind are:
 
  * --long (more generic than functional)
  * --func (short for functional)
 
 Any thoughts on which of those (if either) would be better?
 
 Tim

Using --func would be a clean and concise way to specify that. Enhances
readability as well.

// Mike


signature.asc
Description: PGP signature
___
qa-devel mailing list
qa-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Re: advertisement in packaged software (e.g. Firefox)

[Mike Ruckman]

On Wed, 12 Feb 2014 16:58:34 +0100
H. Guémar hgue...@fedoraproject.org wrote:

 My *personal* opinion is that we should disable this kind of feature
 by default.

+1

 Actually, unless it tracks users, i don't think that our guidelines
 forbids it, though it may influence our choice for the packages set
 installed by default.
 
 Has anyone tried to contact Mozilla Corporation about it so we may
 discuss this based on facts ?
 
 H.

Another thing to determine: who can purchase ad-space from Mozilla? Are
our users going to get ads from Canonical or Windows? Of course, this
question goes away if the functionality is disabled or removed, but
something to keep in mind. 

// Roshi


signature.asc
Description: PGP signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Documentation Tools

[Mike Ruckman]

On Wed, 29 Jan 2014 07:32:29 -0500 (EST)
Kamil Paral kpa...@redhat.com wrote:

  I've posted a comparison between Sphinx and Dexy [1] - as well as
  updated the phabricator ticket [2]. The tools are pretty similar in
  what they can produce, so it really comes down to what people are
  comfortable with. The learning curve for Dexy isn't steep, and I
  think it's just enough easier to use compared to Sphinx for our
  purposes.
 
 I wondered why I hadn't seen it at Fedora Planet (neither your
 previous blogpost), and it's because your RSS feed is no longer
 updated: http://roshi.fedorapeople.org/feeds/fedora.atom.xml
 
 
  I wasn't able to find air-tight reasoning for one over the other for
  qa-devel work - but found dexy a bit easier to use and template.
  Source for both tutorials can be found on my bitbucket profile [3].
 
 Thanks. Can you move it into our team repo list?
 https://bitbucket.org/fedoraqa
 
 
  
  // Roshi
  
  [1] http://roshi.fedorapeople.org/comparing-dexy-and-sphinx.html
  [2] https://phab.qadevel.cloud.fedoraproject.org/T39
  [3] https://bitbucket.org/Rorosha/doc-tools
  
 ___
 qa-devel mailing list
 qa-de...@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/qa-devel


I've fixed the RSS issue. As for moving the repo - I think it makes
more sense to move the tutorial source to taskotron (instead of the
team repo list) once we decide the tool we want to use for docs - Unless
there's a real need for the demo to be on the team page that I'm not
seeing.

// Roshi


signature.asc
Description: PGP signature
___
qa-devel mailing list
qa-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Documentation Tools

[Mike Ruckman]

I've posted a comparison between Sphinx and Dexy [1] - as well as
updated the phabricator ticket [2]. The tools are pretty similar in
what they can produce, so it really comes down to what people are
comfortable with. The learning curve for Dexy isn't steep, and I think
it's just enough easier to use compared to Sphinx for our purposes.

I wasn't able to find air-tight reasoning for one over the other for
qa-devel work - but found dexy a bit easier to use and template. Source
for both tutorials can be found on my bitbucket profile [3].

// Roshi

[1] http://roshi.fedorapeople.org/comparing-dexy-and-sphinx.html
[2] https://phab.qadevel.cloud.fedoraproject.org/T39
[3] https://bitbucket.org/Rorosha/doc-tools


signature.asc
Description: PGP signature
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

[Maniphest] [Commented On] T39: Investigate documentation systems for taskotron and related sub-projects

[roshi (Mike Ruckman)]

roshi added a comment.

As per the qa devel meeting [1], I'll initially be doing a comparison between 
Sphinx [2] and Dexy [3] - with examples for both. 

[1] 
http://meetbot.fedoraproject.org/fedora-blocker-review/2014-01-13/fedoraqa-devel.2014-01-13-17.12.html
[2] http://sphinx-doc.org/
[3] http://dexy.it/

TASK DETAIL
  https://phab.qadevel.cloud.fedoraproject.org/T39

To: roshi
Cc: qa-devel, tflink
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Re: [Test-Announce] 2013-12-04 @ 17:00 UTC - F20 Final Blocker Bug Review #4 Minutes

[Mike Ruckman]

Below are the minutes from today's Blocker Review Meeting. We made it
through all the listed blocker and freeze exception proposals. Looking
forward to the Go/No-Go Meeting tomorrow...

==
#fedora-blocker-review: F20-blocker-review
==


Meeting started by pschindl at 17:00:04 UTC.

Minutes:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-04/f20-blocker-review.2013-12-04-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-04/f20-blocker-review.2013-12-04-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-04/f20-blocker-review.2013-12-04-17.00.log.html

Meeting summary
---
* Roll Call  (pschindl, 17:00:08)

* Introduction  (pschindl, 17:02:00)
  * Our purpose in this meeting is to review proposed blocker and
nice-to-have bugs and decide whether to accept them, and to monitor
the progress of fixing existing accepted blocker and nice-to-have
bugs.  (pschindl, 17:02:04)
  * We'll be following the process outlined at:  (pschindl, 17:02:06)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(pschindl, 17:02:07)
  * The bugs up for review today are available at:  (pschindl, 17:02:09)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (pschindl,
17:02:11)
  * The criteria for release blocking bugs can be found at:  (pschindl,
17:02:14)
  * LINK:
https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria
(pschindl, 17:02:16)
  * LINK: https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria
(pschindl, 17:02:18)
  * LINK:
https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria
(pschindl, 17:02:26)
  * 7 Proposed Blockers  (pschindl, 17:02:26)
  * 15 Accepted Blockers  (pschindl, 17:02:27)
  * 2 Proposed Freeze Exceptions  (pschindl, 17:02:27)
  * 14 Accepted Freeze Exceptions  (pschindl, 17:02:27)

* (1026834) method= combined with 'url' in kickstart fails to find
  packages, in certain situations  (pschindl, 17:02:59)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1026834
(pschindl, 17:03:01)
  * Proposed Blocker, anaconda, NEW  (pschindl, 17:03:03)
  * AGREED: 1026834 - RejectedBlocker AcceptedFreezeException -
Non-functional method affects only virt users and post-release users
won't be probably affected. Rejected as blocker but it's consider as
FE  (pschindl, 17:11:18)

* (1037626) AttributeError: can't set attribute  (pschindl, 17:11:34)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037626
(pschindl, 17:11:36)
  * Proposed Blocker, anaconda, MODIFIED  (pschindl, 17:11:38)
  * AGREED: 1037626 - AcceptedBlocker - Broken text installation
violates final criterion: When using the dedicated installer
images, the installer must be able to complete an installation using
the text, graphical and VNC installation interfaces.  (pschindl,
17:15:13)

* (1037767) Text install : Error in sys.excepthook  (pschindl, 17:15:18)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037767
(pschindl, 17:15:20)
  * Proposed Blocker, anaconda, POST  (pschindl, 17:15:22)
  * AGREED: 1037767 - AcceptedBlocker - Reporting failures on ARM
violates criterion: The installer must be able to report failures
to Bugzilla, with appropriate information included.  (pschindl,
17:29:53)

* (1037934) 'unable to allocate aligned partition' errors keep occurring
  when trying to create partitions on iSCSI device, and
  does...other...odd...stuff  (pschindl, 17:30:05)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037934
(pschindl, 17:30:07)
  * Proposed Blocker, anaconda, NEW  (pschindl, 17:30:09)
  * 1037934 - needs more information. Now it's 2:1 against bug. Punt for
more information.  (pschindl, 17:38:01)

* (881624) U.S. keyboard layout used for encryption passphrase entry
  during fedup second phase  (pschindl, 17:38:18)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=881624
(pschindl, 17:38:20)
  * Proposed Blocker, fedup, NEW  (pschindl, 17:38:22)
  * LINK:

http://meetbot.fedoraproject.org/fedora-meeting-1/2013-01-03/f18_final_gono-go_meeting.2013-01-03-17.01.log.txt
is the log of previous discussion , search '881624' to find it
(adamw, 17:42:44)

* (1036961) Setting up bridge via NetworkManager gui in Gnome fails
  (pschindl, 17:55:49)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1036961
(pschindl, 17:55:51)
  * Proposed Blocker, NetworkManager, NEW  (pschindl, 17:55:53)
  * AGREED: 1036961 - RejectedBlocker - Non-functional bridge
NetworkManager setting is not considered as essential funcionality.
(pschindl, 17:59:47)

* (1037688) /root has 755 permissions - should be 550  (pschindl,
  18:00:13)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037688
(pschindl, 18:00:15)
  * Proposed Blocker, rootfiles, MODIFIED  (pschindl, 18:00:17)
  * AGREED: 

Re: [Test-Announce] 2013-12-02 @ 17:00 UTC (or directly after QA meeting) - F20 Final Blocker Bug Review #3.5 Minutes

[Mike Ruckman]

Below are the minutes from today's Blocker Review Meeting. We made it
through all the listed blocker and freeze exception proposals. 

The next meeting will be 2013-12-04 at 17:00 UTC.

==
#fedora-blocker-review: F20-blocker-review
==


Meeting started by roshi at 17:02:22 UTC. The full logs are available at
Minutes:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-02/f20-blocker-review-%234.2013-12-02-17.02.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-02/f20-blocker-review-%234.2013-12-02-17.02.txt
Log:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-02/f20-blocker-review-%234.2013-12-02-17.02.log.html
 .



Meeting summary
---
* Roll Call  (roshi, 17:03:17)

* Introduction  (roshi, 17:04:05)
  * Our purpose in this meeting is to review proposed blocker and
nice-to-have bugs and decide whether to accept them, and to monitor
the progress of fixing existing accepted blocker and nice-to-have
bugs.  (roshi, 17:04:06)
  * We'll be following the process outlined at:  (roshi, 17:04:06)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 17:04:06)
  * The bugs up for review today are available at:  (roshi, 17:04:06)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
17:04:06)
  * The criteria for release blocking bugs can be found at:  (roshi,
17:04:07)
  * LINK:
https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria
(roshi, 17:04:07)
  * LINK: https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria
(roshi, 17:04:08)
  * LINK:
https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria
(roshi, 17:04:08)

* (1008137) BootLoaderError: bootloader install failed  (roshi,
  17:05:47)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1008137   (roshi,
17:05:47)
  * Proposed Blocker, anaconda, NEW  (roshi, 17:05:47)
  * AGREED: - 1008137 - RejectedBlocker - Without solid reproduction
steps, this isn't considered a blocker.  (roshi, 17:17:38)

* (1008732) LUKSError: luks device not configured  (roshi, 17:17:50)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1008732   (roshi,
17:17:50)
  * Proposed Blocker, anaconda, NEW  (roshi, 17:17:50)
  * AGREED: - 1008732 - RejectedBlocker - There are no recent
reproducers or crash reports associated with this bug and is thusly
not considered a blocker.  (roshi, 17:20:48)

* (1026834) method= combined with kickstart uses invalid repository
  (roshi, 17:21:04)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1026834   (roshi,
17:21:04)
  * Proposed Blocker, anaconda, NEW  (roshi, 17:21:04)
  * AGREED: - 1026834 - Punt - Putting off a decision until this is
reproduced with TC4. Please vote on blocker status in ticket.
(roshi, 17:30:01)

* (1035799) f20 tc3, adding a new mount point, desired capacity empty,
  crash  (roshi, 17:30:20)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1035799   (roshi,
17:30:20)
  * Proposed Blocker, anaconda, POST  (roshi, 17:30:20)
  * AGREED: - 1035799 - AcceptedBlocker - This bug violates the Final
criteria: The installer must be able to create and install to any
workable partition layout...   (roshi, 17:38:06)

* (1036705) BootLoaderError: bootloader install failed when /boot on LV
  (roshi, 17:38:30)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1036705   (roshi,
17:38:30)
  * Proposed Blocker, anaconda, NEW  (roshi, 17:38:30)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1008137#c18
(Viking-Ice, 17:42:55)
  * AGREED: - 1036705 - AcceptedBlocker - This bug violates the Final
criteria: The installer must be able to create and install to any
workable partition layout...   (roshi, 17:47:52)

* (1035533) Fedora 20 final fedora-release and generic-release packages
  required for GA  (roshi, 17:48:03)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1035533   (roshi,
17:48:03)
  * Proposed Blocker, fedora-release, ON_QA  (roshi, 17:48:03)
  * AGREED: - 1035533 - AcceptedBlocker - This violates the final
criteria: A fedora-release package containing the correct names,
information and repository configuration for a final Fedora release
must be present on release-blocking images ...  (roshi, 17:50:26)

* (1035531) Fedora 20 final release notes required for GA  (roshi,
  17:50:41)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1035531   (roshi,
17:50:41)
  * Proposed Blocker, fedora-release-notes, NEW  (roshi, 17:50:41)
  * AGREED: - 1035531 - AcceptedBlocker - This violates the final
criteria: The final branded release notes must be present on
release-blocking images and the appropriately versioned generic
release notes must be available in the release repository...
(roshi, 17:52:21)

* (1024223) fedup 19-20 failed with DVD iso upgrade  (roshi, 17:53:03)
 

2013-11-27 @ **17:00 UTC** - F20 Final Blocker Bug Review #3 Minutes

[Mike Ruckman]

Below are the minutes from today's Blocker Review Meeting. We made it
through all the listed blocker (10) and freeze exception (14)
proposals. 

The next meeting will be 2013-12-04 at 17:00 UTC.

==
#fedora-blocker-review: F20-blocker-review
==


Meeting started by roshi at 17:01:06 UTC. 

Minutes:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-27/f20-blocker-review-3.2013-11-27-17.01.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-27/f20-blocker-review-3.2013-11-27-17.01.txt
Log:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-27/f20-blocker-review-3.2013-11-27-17.01.log.html


Meeting summary
---
* Roll Call  (roshi, 17:01:38)

* Introduction  (roshi, 17:02:53)
  * Our purpose in this meeting is to review proposed blocker and
nice-to-have bugs and decide whether to accept them, and to monitor
the progress of fixing existing accepted blocker and nice-to-have
bugs.  (roshi, 17:02:53)
  * We'll be following the process outlined at:  (roshi, 17:02:54)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 17:02:54)
  * The bugs up for review today are available at:  (roshi, 17:02:54)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
17:02:54)
  * The criteria for release blocking bugs can be found at:  (roshi,
17:02:55)
  * LINK:
https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria
(roshi, 17:02:55)
  * LINK: https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria
(roshi, 17:02:56)
  * LINK:
https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria
(roshi, 17:02:56)
  * 10 Proposed Blockers  (roshi, 17:03:44)
  * 14 Accepted Blockers  (roshi, 17:03:44)
  * 12 Proposed Freeze Exceptions  (roshi, 17:03:44)
  * 7 Accepted Freeze Exceptions  (roshi, 17:03:44)

* (1032620) Doesn't remember POP password  (roshi, 17:04:42)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1032620   (roshi,
17:04:42)
  * Proposed Blocker, evolution, ASSIGNED  (roshi, 17:04:42)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1032531
(Viking-Ice, 17:09:12)
  * AGREED: - 1032620 RejectedBlocker - While this is an issue, there
doesn't seem to be enough people affected in order to be considered
a blocker for Final Release.  (roshi, 17:10:59)

* (960381) gnome-shell eats a lot of mem  (roshi, 17:11:12)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=960381   (roshi,
17:11:13)
  * Proposed Blocker, gnome-shell, NEW  (roshi, 17:11:13)
  * AGREED: - 960381 RejectedBlocker - While this is an issue, there
doesn't seem to be enough people affected in order to be considered
a blocker for Final Release. If reproduction steps are found, please
re-propose.  (roshi, 17:14:00)

* (969524) plasma widgets unclickable on arm  (roshi, 17:14:14)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=969524   (roshi,
17:14:15)
  * Proposed Blocker, kdelibs, NEW  (roshi, 17:14:15)
  * AGREED: - 969524 AcceptedBlocker - This bug clearly violates the
default panel functionality release criteria: All elements of the
default panel (or equivalent) configuration in all release-blocking
desktops must function correctly in typical use.   (roshi,
17:18:40)

* (1004621) plasma-nm doesn't attempt to connect to any listed networks
  on Fedora KDE live  (roshi, 17:18:52)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1004621   (roshi,
17:18:53)
  * Proposed Blocker, kde-plasma-nm, ON_QA  (roshi, 17:18:53)
  * LINK:

https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Default_panel_functionality
(adamw, 17:25:57)
  * AGREED: - 1004621 AcceptedBlocker - This bug violates the Final
release criteria Default Panel Functionality: All elements of the
default panel (or equivalent) configuration in all release-blocking
desktops must function correctly in typical use.   (roshi,
17:27:41)

* (1034701) When installing F20 from PXE, after clicking on disk
  management, GUI is horribly lagging and 'loop1' process consumes 100%
  of CPU  (roshi, 17:28:09)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1034701   (roshi,
17:28:09)
  * Proposed Blocker, kernel, NEW  (roshi, 17:28:09)
  * AGREED: - 1034701 RejectedBlocker - This bug does not seem to be
reproducible or affect a large set of users so is not considered a
Final Blocker. If reproduction steps can be found, please
re-propose.  (roshi, 17:33:53)

* (1035000) SELinux issue when dealing with big_key support  (roshi,
  17:34:02)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1035000   (roshi,
17:34:02)
  * Proposed Blocker, kernel, NEW  (roshi, 17:34:02)
  * LINK: http://fpaste.org/57269/13855742/ is the IRC discussion from
yesterday  (adamw, 17:43:28)
  * AGREED: - 1035000 RejectedBlocker AcceptedFreezeException - This 

[Test-Announce] 2013-11-27 @ **17:00 UTC** - F20 Final Blocker Bug Review #3

[Mike Ruckman]

# F20 Final Blocker Review meeting #3
# Date: 2013-11-27
# Time: 17:00 UTC (12:00 EST, 09:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net

Freeze is now upon us and tomorrow (2013-11-27)
we'll be having another Blocker Review Meeting for Fedora 20.
There's plenty to review this time around with a whopping 10 proposed
blockers and 10 proposed freeze exceptions. The full list is located here:
http://qa.fedoraproject.org/blockerbugs/current it might be worth the
time to read up on them before the meeting - that way
we can get through them all in the mere 3 hours we have.

We'll be reviewing the bugs to ensure they meet the Final release
criteria [1] as blocking final release and that the bugs are getting
the attention they need.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[1] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2013-11-20 @ **17:00 UTC** - F20 Final Blocker Bug Review #2

[Mike Ruckman]

# F20 Final Blocker Review meeting #2
# Date: 2013-11-20
# Time: 17:00 UTC (12:00 EST, 09:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net

It's that time again! Tomorrow (2013-11-20) we'll be having another
Blocker Review Meeting for Fedora 20. We currently have 6 proposed
blockers and 3 proposed freeze exceptions to review. The full
list is located here: http://qa.fedoraproject.org/blockerbugs/current

We'll be reviewing the bugs to ensure they meet the Final release
criteria [1] as blocking final release and that the bugs are getting
the attention they need.

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[1] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria

==
// Mike
Fedora QA
irc: roshi | twitter: roshi_fedora 
blog: roshi.fedorapeople.org


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2013-11-14 @ **17:00 UTC** - F20 Final Blocker Bug Review #1.5

[Mike Ruckman]

# F20 Final Blocker Review meeting #1.5
# Date: 2013-11-14
# Time: 17:00 UTC (12:00 EST, 09:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net

Despite the fact that we *just had* a Blocker Review Meeting, we get to
have another one tomorrow (2013-11-14) to finish the rest of the
proposed blockers! There were 20 proposed this morning when we started
and there are 6 remaining (though, who knows by tomorrow). We also
still have 4 proposed Freeze Exceptions to evaluate. The full list is
located here: http://qa.fedoraproject.org/blockerbugs/current

We'll be reviewing the bugs to ensure they meet the Final release
criteria [1] as blocking final release and that the bugs are getting
the attention they need. 

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 - check out the SOP on the wiki:
  - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you tomorrow!

[1] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria

==
// Mike
Fedora QA
irc: roshi | twitter: roshi_fedora 
blog: roshi.fedorapeople.org


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] 2013-11-13 @ **17:00 UTC** - F20 Final Blocker Bug Review #1

[Mike Ruckman]

# F20 Final Blocker Review meeting #1
# Date: 2013-11-13
# Time: 17:00 UTC (12:00 EST, 09:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net

It's time for the first Fedora 20 Final Blocker Review meeting! We'll
be running through the final blockers and freeze exception bugs. To date
we have 16 proposed blockers and 4 proposed FE's. The current list is
available at: http://qa.fedoraproject.org/blockerbugs/current

We'll be reviewing the bugs to determine ...

1. Whether they meet the beta release criteria [1] and should stay on
the list
2. Whether they are getting the attention they need

[1] http://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria

For guidance on Blocker and FreezeException bugs, please refer to
  - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
  - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

For the blocker review meeting protocol, see
  -https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

See you there!

==
// Mike
Fedora QA
irc: roshi | twitter: roshi_fedora 
blog: roshi.fedorapeople.org


signature.asc
Description: PGP signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct