[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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org

Re: Schedule concern next week: holidays ahead!

[Mike Ruckman]

> 
> Given the urgency of the situation, please schedule a blocker meeting for
> today (formally or informally).

I'll be ready to run a meeting at the usual 1600 UTC time in 
#fedora-blocker-review.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Self-introduction: suiwenfeng

[Mike Ruckman]

On Mon, Jun 26, 2017 at 12:50:18PM +, ? ?? wrote:
> Hi guys,
> 
> 
> 
> I'm very glad to request to join Fedora QA Work Group. Now I have 2 years 
> work experience on Hadoop/Storm/Kafka. I am familiar with Java/Scala/Python, 
> and interested in Fedora Cloud. Hope I can start from QA and take part in 
> some works of Fedora Cloud.
> 
> 
> 
> It`s about 5 years ago, I am start using Fedora 16. And when I come back, 
> it`s 27 now... Anyway, it is really a fancy work. When I have no idea how to 
> contribute to it, Mike Ruckman`s comment guides me to the place.
> 
> 
> 
> My name is suiwenfeng, I'm 24 years old and live at Shanghai. I have more 
> than 8 hours per weeks to make some contributions. Below is my contacts.
> 
> 
> 
> Github: https://github.com/suiwenfeng
> 
> IRC: suiwenfeng AT chat.freenode.net
> 
> FAS/Bugzilla: suiwenf...@live.cn
> 
> 
> 
> Thanks
> 
> suiwenfeng

Welcome Suiwenfeng! Looking forward to working in both QA and Cloud with
you! Please let me know via IRC or email if you have any questions!

// Mike
--
Fedora QA
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org

Re: New Blocker Criterion Proposal: Same default packages for all arches

[Mike Ruckman]

On Wed, May 10, 2017 at 04:52:05PM +0200, Kamil Paral wrote:
> I don't really understand this, and I haven't read the meeting log, so I
> apologize if my questions are dumb.

I was in the meeting, and I was confused - so your questions aren't
dumb. :)

> Why would we dictate that Editions/Spins can't use different software on
> different architectures? It might make perfect sense to use browser X on
> x86_64 because it's very good, but use browser Y on i386 because of memory
> limitations of i386 arch (browser Y needing much less memory than browser
> X). Similarly, if shell A no longer supports i386, why would be ban it from
> being preinstalled on x86_64? i386 would have shell B instead. Those are
> random examples, but it seems to me that they can be completely valid. If
> there's such requirement that Editions/Spins can't install different
> software on different arches, I think that should be established by FESCo,
> not us.

I concur with Kamil on this one, I think there's valid reasons a package
set might be different based on the arch. If this is indeed the
direction we want to go, I think FESCo needs to make that call.

> For this particular Firefox example, what is the core problem that you're
> trying to fix here? Is it the fact that Firefox excluded many arches from
> builds? From my QA POV, since it excluded arm, it's a blocker, since arm is
> primary. If it hadn't excluded arm, it would not be a blocker, and
> alternate arches would need to find a way (fix the bug or use a different
> browser). If you still think this should not happen, you could ask FESCo to
> present some rules saying when Fedora packagers can exclude other arches
> from the build and when they can't. We could then enforce that (instead of
> prohibiting different package sets).

As I think I said in the meeting, I thought the bug as filed was the
blocker and didn't see the need for the shadow bug created to track
blockeriness. It was a secondary affect, sure; but we deal with that all
the time. I concur that it might be a good idea to keep a list (FESCo
generated probably?) of "key" packages that need to be available on all
arches, or what arches they're allowed to not use.

// Mike
--
Fedora QA
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org

Re: Validation proposal: separate out artwork / release identification checks to their own test case

[Mike Ruckman]

On Wed, Apr 05, 2017 at 03:38:00PM -0700, Adam Williamson wrote:
> Hi folks! Time for another proposal :)
> 
> We currently kinda bundle the checks for correct artwork and 'release
> identification' (stuff that identifies the release, like 'Welcome to
> Fedora 26!' etc.) into two test cases that also include functionality
> testing:
> 
> https://fedoraproject.org/wiki/QA:Testcase_base_startup
> https://fedoraproject.org/wiki/QA:Testcase_base_initial_setup
> 
> This is a bit awkward, and also is a bit of a problem for automation.
> We could actually automate the functional parts of those tests in
> openQA (I've just finished adding openQA tests that install without a
> user account and check gnome-initial-setup and initial-setup work OK),
> but we can't really automate the 'release identification' / artwork
> checks. So we can't have openQA report wiki passes for these tests, so
> long as they're combined like this.
> 
> So I'm proposing we separate out a new 'artwork and release
> identification' test case. I've written a draft of it:
> 
> https://fedoraproject.org/wiki/User:Adamwill/Draft_Testcase_artwork_release_identification
> 
> We would remove the relevant bits from the other two test cases.
> 
> I'm a bit in two minds about what to do with the matrices. I'm thinking
> we could either add this test case to the Server, Cloud and Desktop
> pages, or we could put it in the Base page (as the current tests are).
> Looking at this, it occurs to me that not just these checks but most of
> the other Base tests would actually be relevant to things beyond the
> 'environments' currently in the Base page (Workstation, Server, KDE,
> ARM and Cloud). I'm thinking perhaps we could rejig the page a bit, and
> add another table with non-blocking columns for other desktops and
> stuff.
> 
> Thoughts? Thanks!
> -- 
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net

Sounds good to me.

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

Re: Criteria proposal: move "No broken packages" requirement to Final

[Mike Ruckman]

On Wed, Apr 05, 2017 at 11:17:27AM -0700, Adam Williamson wrote:
> So, at the Alpha go/no-go we discussed this bug:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1437299
> 
> and agreed that with current behaviour of anaconda and dnf, blocking
> Alpha release on it didn't make sense.
> 
> The relevant criterion here is 
> https://fedoraproject.org/wiki/Fedora_26_Alpha_Release_Criteria#No_broken_packages
>  :
> 
> "There must be no errors in any package on the release-blocking images
> which cause the package to fail to install."
> 
> In practice, this criterion is only relevant to DVD images. AFAIK, it's
> not possible for the other image types to contain packages they can't
> install, because they all wind up deploying the bits they're actually
> built *from* - they don't act as 'package repositories'.
> 
> At the time we wrote the criterion, we had a generic DVD image with
> many different packages and package groups on it. The installer GUI
> allowed you to select 'optional' packages from the groups included on
> the image for installation. And if any package selected had dependency
> issues, the install would fail with an error.
> 
> Quite a lot has changed since. We no longer have a generic DVD image,
> only the Server DVD image, which contains only a handful of Server-
> related package groups. The installer GUI no longer lets you select
> optional packages; you can only select the 'environments' and 'option
> groups' that are present on the DVD, and only 'mandatory' and 'default'
> packages from those groups will be selected for install. And if a
> selected package has dependency issues, the install will simply proceed
> with that package (and anything else that requires it) omitted.
> 
> Given all of these considerations, I propose we move the criterion to
> Final.
> 
> For the record, I'm also looking at the dnf/anaconda behaviour. It
> turns out there's a few wrinkles, but I do think we should switch it
> back to 'strict' mode (where any listed package not being found or
> being non-installable for some reason causes an error) by default. But
> it's not entirely straightforward.
> https://bugzilla.redhat.com/show_bug.cgi?id=1427365 is the place to
> follow that. I do still think that moving the criterion to Final would
> be OK even if we changed dnf behaviour; I think for Alpha and Beta it's
> enough if the default Server DVD package set installs OK, we should
> make sure that the other package sets available from the Server DVD
> install OK for Final.
> 
> Thoughts? Notes? Concerns? Thanks!
> -- 
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net

I'm +1 to the movement to Final.

// Mike
--
Fedora QA
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org

Re: Release validation testers: a question

[Mike Ruckman]

On Tue, Feb 14, 2017 at 12:02:14PM -0800, Adam Williamson wrote:
> Hi folks! I've got a question for everyone who helps out with release
> validation testing. It's related to the project to build a new system
> for submitting those results. We have a ticket for designing that
> system:
> 
> https://pagure.io/design/issue/483
> 
> and as part of the discussion there, we're wondering something. Given
> that it's part of the new design that there's some kind of step where
> you specify which particular image you're testing, does it make more
> sense to you if you choose things in this order:
> 
> 1. Pick a test to run
> 2. Pick an image to run the test on
> 
> Or this order:
> 
> 1. Pick an image to test
> 2. Pick a test to run on the image
> 
> ? It's pretty important to the design approach. Thanks!
> 
> (Please do feel free to read the ticket and mention any other thoughts
> you have on the design, too.)
> -- 
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net

I also pick an image and then run tests against it.

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

Re: criterion adjustment proposal: demote optical media support

[Mike Ruckman]

On Tue, Jan 17, 2017 at 08:41:57AM -0500, Kamil Paral wrote:
> Hi,
> 
> as discussed in "future of official optical media support in Fedora" thread 
> in devel list [1], we agreed to decrease the importance and testing of 
> optical media support for Fedora release composes, and block on just several 
> specific images. This is a concrete proposal to adjust our release criteria 
> to match the outcome of the discussion. The outcome is that we will not block 
> on broken optical support for any Alpha/Beta composes, and we will block on 
> optical support for Final composes only for Workstation Live and Everything 
> netinst image (please note that I didn't receive much feedback for my last 
> point where I suggested Everything netinst is made release blocking [2] - if 
> you have something to add, there's still time).
> 
> 
> == Don't block on Alpha/Beta adjustment ==
> 
> 1. On page 
> https://fedoraproject.org/wiki/Fedora_26_Alpha_Release_Criteria#Release-blocking_images_must_boot
>  the first sentence under "Supported media types" section changes from:
> > Release-blocking live and dedicated installer images must boot when written 
> > to optical media of an appropriate size (if applicable) and when written to 
> > a USB stick with at least one of the officially supported methods.
> to
> > Release-blocking live and dedicated installer images must boot when written 
> > to a USB stick with at least one of the officially supported methods.
> 
> 2. On page 
> https://fedoraproject.org/wiki/Fedora_26_Beta_Release_Criteria#Release-blocking_images_must_boot
>  the first sentence under "Supported media types" section changes from:
> > Release-blocking live and dedicated installer images must boot when written 
> > to optical media of an appropriate size (if applicable) and when written to 
> > a USB stick with any of the officially supported methods.
> to
> > Release-blocking live and dedicated installer images must boot when written 
> > to a USB stick with any of the officially supported methods.
> 
> 3. On page https://fedoraproject.org/wiki/Fedora_26_Final_Release_Criteria we 
> add "Initialization requirements" header with "Release-blocking images must 
> boot" sub-header (same as in Alpha/Beta) with text:
> > All release-blocking images must boot in their supported configurations.
> > Supported media types [hide]
> > Release-blocking live and dedicated installer images must boot when written 
> > to optical media of an appropriate size (if applicable) and when written to 
> > a USB stick with any of the officially supported methods.
> > Difference from Beta [hide]
> > This criterion differs from the similar Beta criterion only in that it 
> > requires all supported images to work when written also to an optical 
> > media, not just USB sticks.
> 
> 
> == Block only on Workstation Live and Everything netinst change ==
> 
> 1. On page 
> https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fedora26
>  we add another column to the all the tables called "optical boot is release 
> blocking". The cells will have value "yes" for Workstation Live x86_64 and 
> Everything netinst x86_64, value "no" for all other rows containing "release 
> blocking = yes", and will be grayed out for rows containing "release blocking 
> = no".
> 
> (We link to this page from Alpha/Beta/Final release criteria pages from the 
> last sentence in the description in the top of the page.)
> 
> 
> == Wiki adjustments ==
> 
> 1. On page 
> https://fedoraproject.org/wiki/Template:Installation_test_matrix#Default_boot_and_install_.28x86_64.29
>  we change "Expected coverage" box from:
> > For Alpha and Beta, we expect a reasonable sampling of tests across the 
> > table, with at least some testing for all three media types, both firmware 
> > types, and each major class of deliverable (netinst, live and DVD). For 
> > Final, we expect full coverage for all the Alpha / Final rows.
> to
> > For Alpha and Beta, we expect a reasonable sampling of tests across the 
> > table, with at least some testing for VM and USB boot method, both firmware 
> > types, and each major class of deliverable (netinst, live and DVD). Optical 
> > boot testing is optional at this stage. For Final, we expect full coverage 
> > for the Alpha / Final rows with VM and USB boot method. Optical boot 
> > testing in Final is mandatory for 
> > [[Fedora_Program_Management/ReleaseBlocking/Fedora26|supported images]].
> 
> 
> Wording improvements or any other feedback welcome.
> 
> Thanks,
> Kamil
> 
> [1] 
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/KICRVUS3YHNTLHY47O5A2XL2C5YMCFIH/
> [2] 
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/VQQXMJ7QMTLNRFRI5VYIKGIU5IV2W6KB/

+1 for those changes.

Thanks Kamil!

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
___
test mailing list -- test@lists.fedoraproject.org

Re: First Bug Report

[Mike Ruckman]

> - Original Message -
> From: "Allan Mwenda" 
> To: test@lists.fedoraproject.org
> Sent: Friday, December 23, 2016 12:54:35 AM
> Subject: First Bug Report

> Hell everyone,
> So I posted my first bug on bugzilla, not sure if i did it exactly right
> but i gave it my best shot. Still learning, cheers.
> https://bugzilla.redhat.com/show_bug.cgi?id=1408323

Welcome to Fedora QA, Allan! Thanks for the bug report; it looks like you
have a good handle on things. Have you read the Join page on the wiki [0]?
It has a good list of other places to get involved with as well.

[0] https://fedoraproject.org/wiki/QA/Join

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

Hiatus

[Mike Ruckman]

Greetings list!

I wanted to give a heads up to the list that due to some personal stuff, I
will be taking a hiatus from my regularly scheduled activities. I'll still
be filing test results and sporadically responding to emails - but you won't
be likely to find me in our usual meetings and whatnot.

Rest assured, everything is fine and I will get back into things; I just
have to take care of some stuff.

Thanks!

--
// Mike
--
Fedora QA
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: [F24 Criteria Change] Cockpit Release Criteria

[Mike Ruckman]

On Thu, Oct 22, 2015 at 02:35:11PM -0400, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Recently, we discovered a bug in gnutls that caused Cockpit to be
> unreachable by recent versions of Google Chrome. It was ambiguous what
> the release criteria actually means, since it didn't specify which
> browser applications were blocking. I'd like to propose the following
> additional wording for Cockpit criteria:
> 
> * All Cockpit functional criteria must be satisfied when the user is
> running any of the following blocking browsers:
>  - Mozilla Firefox as shipped in the same Fedora release
>  - Mozilla Firefox of the latest available version on Windows at
>compose time.
>  - Mozilla Firefox of the latest available version on OSX at compose
>time.
>  - Google Chrome of the latest available version on Fedora at compose
>time.
>  - Google Chrome of the latest available version on Windows at compose
>time.
>  - Google Chrome of the latest available version on OSX at compose time.
> 
> 
> Alternately, we could decide that it's only *blocking* if the above
> browsers work with Cockpit when the browser is running on Fedora, but
> that is somewhat at odds with our reasoning for having a management
> console as a web UI in the first place: that it is accessible
> regardless of the client system.
> 
> Comments welcome, but please keep replies on the
> test@lists.fedoraproject.org list, as that's where criteria decisions
> are made.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iEYEARECAAYFAlYpLFwACgkQeiVVYja6o6NF/wCgg6iot1JKOfmAbTZMboBcPvs5
> ZIIAnA+YxRAjPMt69lqv2nOR7qXnCYnV
> =PIuy
> -END PGP SIGNATURE-

I'm +1 in general to these criteria. As Dennis said, we just need to
make sure we have access to Windows/OSX in order to actually do the
testing.

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [F24 Criteria Change] Cockpit Release Criteria

[Mike Ruckman]

On Fri, Oct 23, 2015 at 07:41:56AM -0500, Dennis Gilmore wrote:
> On Thursday, October 22, 2015 02:35:11 PM Stephen Gallagher wrote:
> > Recently, we discovered a bug in gnutls that caused Cockpit to be
> > unreachable by recent versions of Google Chrome. It was ambiguous what
> > the release criteria actually means, since it didn't specify which
> > browser applications were blocking. I'd like to propose the following
> > additional wording for Cockpit criteria:
> > 
> > * All Cockpit functional criteria must be satisfied when the user is
> > running any of the following blocking browsers:
> >  - Mozilla Firefox as shipped in the same Fedora release
> >  - Mozilla Firefox of the latest available version on Windows at
> >compose time.
> >  - Mozilla Firefox of the latest available version on OSX at compose
> >time.
> >  - Google Chrome of the latest available version on Fedora at compose
> >time.
> >  - Google Chrome of the latest available version on Windows at compose
> >time.
> >  - Google Chrome of the latest available version on OSX at compose time.
> > 
> > 
> > Alternately, we could decide that it's only *blocking* if the above
> > browsers work with Cockpit when the browser is running on Fedora, but
> > that is somewhat at odds with our reasoning for having a management
> > console as a web UI in the first place: that it is accessible
> > regardless of the client system.
> 
> I think that it is fine. But you need to make sure you have resources 
> available to test on Windows and OS X. I wonder what can be done to do 
> automated testing on the platforms to ensure things work. I would like to 
> have 
> us try and automate most if not all of the validation,  at least in a basic 
> level.
> 
> Dennis 

FWIW, I'm willing to help write some selenium [0] tests for validating
cockpit. Depending on if we can get licenses for the different OSs we
want to validate against, we could also set up a grid [1] for that.

It's been a while since I've worked with selenium, but I don't think
it'd take me long to get back up to speed.

[0] http://www.seleniumhq.org/
[1] https://github.com/SeleniumHQ/selenium/wiki/Grid2

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Proposed new blocking criterion for Fedora Server: GSSAPI SSO via SSH

[Mike Ruckman]

On Mon, Oct 05, 2015 at 03:05:42PM -0400, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Currently, we have a number of blocking criterion in Fedora Server
> around domain membership that the machine must be able to join a
> domain and that a user must be able to log into the machine using
> standard login mechanisms (console, GDM, etc.).
> 
> What we are lacking is a criterion specifying single-sign-on
> functionality, which is a key part of the domain experience. I'd like
> to propose that the following functionality be added as a Beta
> criterion from here forth:
> 
> == Server Product Requirements ==
> 
> === Remote Authentication ===
> * A user who signs in locally or via SSH to a Fedora Server joined to
> a FreeIPA or Active Directory domain using a supported domain-joining
> mechanism[1] must be capable of connecting via SSH to any other Fedora
> Server of the same version to which they have appropriate access
> privileges without being required to re-enter their password.[2]
> (Note: this assumes an "online" login; if the user logs in while
> disconnected from the authentication server, they may not be able to
> use SSO features without manual intervention.)
> 
> * Single-sign-on capabilities must be available without any additional
> configuration by the user except the initial join to the domain.
> 
> 
> 
> [1] This means realmd in the current implementation, which is the
> mechanism used under the hood by Cockpit. I'd recommend leaving out
> more manual methods like ipa-client-install, adcli and 'net ads'.
> 
> [2] Under the hood, this means that the authentication negotiation
> should happen via GSSAPI.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iEYEARECAAYFAlYSygMACgkQeiVVYja6o6NUMwCgkNjoXxlGB6cyCZC3bkVJ1pNX
> +K4AoJn6Yg24djVWofsN5qr9AhGoBdDn
> =vY35

+1

That seems to be clear and make sense to me.

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

Re: Fedora Council report

[Mike Ruckman]

On Mon, Jun 01, 2015 at 01:33:19PM -0600, Mike Ruckman wrote:
 Since we decided right after the QA meeting that I'd be filling in as
 the QA rep for this meeting - I figured I'd ping the list to see if
 anyone had anything else they wanted to include?
 
 Kamil will be sending out his additions (probably tomorrow), and then
 I'll be making a slide deck for the hangout. It would also be good if we
 all watched the meeting as it was taking place; I'm sure the council
 will have questions for us as a group.
 
 Thanks!
 

Thanks for the feedback! I've created and uploaded a slide deck for 
the report on the wiki [0]. It doesn't go into much detail in the 
slides, but please let me know if it looks like I missed anything.

Thanks!

[0] https://fedoraproject.org/wiki/User:Roshi/QA/CouncilReportSlides

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora Council report

[Mike Ruckman]

On Mon, May 18, 2015 at 08:57:26AM -0400, Kamil Paral wrote:
  Hi, folks! So I'm following up again on the request from the Council
  that we send someone to report on the QA project's status. The proposed
  date was 2015-06-08.
  
  At the last QA meeting (on 2015-05-04) I volunteered to do it, then
  realized I won't be able to on 2015-06-08 as I'll be on a plane. So, we
  have two choices: either someone else volunteers to do the report, or
  we ask the Council if we can change the date. Is anyone else interested
  in doing the report? Please reply if so!
 
 Thanks, Adam, for looking into this. You'll probably already on vacation, so 
 I assume you won't be reading this until the actual council meeting. But if 
 you did...
 
 If needed, I'm happy to fill in for you. But if you wanted to be actively 
 part of the discussion, I can also ask the council to move the date. You seem 
 to have given quite some thought into those issues. I won't be able to look 
 into it properly before we push F22 out of the door, but that should 
 hopefully happen way before the council meeting, so then I can try to expand 
 the points you mentioned below.
 
 If there are some other volunteers to take care of this, I'm even more happy 
 to pass this onto you :-)
 
 Kamil
 

Since we decided right after the QA meeting that I'd be filling in as
the QA rep for this meeting - I figured I'd ping the list to see if
anyone had anything else they wanted to include?

Kamil will be sending out his additions (probably tomorrow), and then
I'll be making a slide deck for the hangout. It would also be good if we
all watched the meeting as it was taking place; I'm sure the council
will have questions for us as a group.

Thanks!

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

2015-05-18 @ 1600 UTC ** Blocker Review Minutes

[Mike Ruckman]

The minutes to this meeting can be found here:
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-05-18/f22-blocker-review.2015-05-18-16.00.html

Thanks!

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

2015-04-06 @ 1600 UTC ** F22 Blocker Review Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 16:00:03 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-04-06/f22-blocker-review.2015-04-06-16.00.log.html
.

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

* Introduction  (roshi, 16:03:28)
  * 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, 16:03:28)
  * We'll be following the process outlined at:  (roshi, 16:03:32)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 16:03:35)
  * The bugs up for review today are available at:  (roshi, 16:03:37)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
16:03:40)
  * The criteria for release blocking bugs can be found at:  (roshi,
16:03:42)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 16:03:45)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 16:03:48)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 16:03:51)

* (1185117) Custom partitioning does not allow convenient removal of
  volume including snapshots (btrfs, LVM)  (roshi, 16:04:27)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1185117   (roshi,
16:04:30)
  * Proposed Blocker, anaconda, NEW  (roshi, 16:04:32)
  * AGREED: - 1185117 - RejectedBlocker Beta - This is a conditional
violation of the criterion must be able to remove volumes, but it
is an uncommon situation and too technically complex to resolve in
Fedora 22  (sgallagh, 16:26:10)

* (1206472) AttributeError: 'NoneType' object has no attribute
  'set_focus_vadjustment'  (roshi, 16:26:30)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1206472   (roshi,
16:26:34)
  * Proposed Blocker, anaconda, POST  (roshi, 16:26:36)
  * AGREED: - 1206472 - AcceptedBlocker Beta - This bug is a clear
violation of the following criteria when using a proxy: When using
the dedicated installer images, the installer must be able to use
HTTP, FTP and NFS repositories as package sources.  (roshi,
16:30:20)

* (1208979) LUKSError: luks device not configured  (roshi, 16:30:28)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1208979   (roshi,
16:30:28)
  * Proposed Blocker, anaconda, NEW  (roshi, 16:30:28)
  * LINK:

https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Custom_partitioning
(nirik, 16:33:10)
  * AGREED: - 1208979 - AcceptedFreezeException Beta AcceptedBlocker
Final - This bug conditionally violates the custom partition
criterion for final but we would accept a fix for Beta during
freeze.  (roshi, 16:37:47)

* (1209140) Upgrades from Fedora 21 break tomcat service  (roshi,
  16:37:53)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1209140   (roshi,
16:37:53)
  * Proposed Blocker, dogtag-pki, NEW  (roshi, 16:37:54)
  * AGREED: - This bug isn't a blocker any more, nomination withdrawn.
(roshi, 16:39:42)

* (1164492) Please drop libvirt 'default' network dependency for F22
  (roshi, 16:39:45)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1164492   (roshi,
16:39:48)
  * Proposed Blocker, gnome-boxes, NEW  (roshi, 16:39:51)
  * AGREED: - 1164492 - AcceptedBlocker Beta - We're reaffirming this
bugs status from F21 to F22. The end result of this bug is bad
enough that it warrants blocker status to get the fix in for beta.
(roshi, 16:44:24)

* (1205534) gnome-initial-setup crashes upon selecting language  (roshi,
  16:44:45)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1205534   (roshi,
16:44:49)
  * Proposed Blocker, gnome-initial-setup, NEW  (roshi, 16:44:51)
  * AGREED: - 1205534 - Punt - Waiting until someone can reproduce and
then will discuss in comments.  (roshi, 16:50:08)

* (1146232) No network connection in virtual guest when libvirt in the
  guest tries to use the same IP address range as the host (still can
  occur when live image used to deploy both host and guest)  (roshi,
  16:50:22)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1146232   (roshi,
16:50:26)
  * Proposed Blocker, libvirt, NEW  (roshi, 16:50:29)
  * AGREED: - 1146232 - RejectedBlocker Beta - This bug is already
covered under RHBZ#1164492 and doesn't need to be listed as another
blocker.  (roshi, 16:57:33)

* (1208536) Problems recognizing BIOS RAID devices  (roshi, 16:57:43)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1208536   (roshi,
16:57:43)
  * Proposed Blocker, python-blivet, POST  (roshi, 16:57:43)
  * AGREED: - 1208536 - AcceptedBlocker Beta - This bug is a clear
violation of the Beta raid criterion: The installer must be able to

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

2015-03-30 @ 1600 UTC ** Blocker Review Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 16:04:24 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-30/f22-blocker-review.2015-03-30-16.04.log.html
.

Meeting summary
---
* Roll Call  (roshi, 16:04:24)

* Introduction  (roshi, 16:07:59)
  * 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, 16:07:59)
  * We'll be following the process outlined at:  (roshi, 16:08:03)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 16:08:05)
  * The bugs up for review today are available at:  (roshi, 16:08:08)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
16:08:10)
  * The criteria for release blocking bugs can be found at:  (roshi,
16:08:13)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 16:08:16)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 16:08:18)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 16:08:22)

* (1206760) KDE desktop doesn't notify for available updates  (roshi,
  16:08:32)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1206760   (roshi,
16:08:33)
  * Proposed Blocker, apper, VERIFIED  (roshi, 16:08:33)
  * AGREED: - 1206760 - AcceptedBlocker Beta - This bug is a clear
violation of the beta criterion: Release-blocking desktops must
notify the user of available updates, but must not do so when
running as a live image.  (roshi, 16:11:54)

* (1206420) docker missing from 22 Beta TC5 x86_64 trees  (roshi,
  16:13:03)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1206420   (roshi,
16:13:03)
  * Proposed Blocker, distribution, ON_QA  (roshi, 16:13:04)
  * AGREED: - 1206420 - AcceptedBlocker Beta - This bug is a clear
violation of the following criterion: When installing with a
release-blocking dedicated installer image, the installer must be
able to install the default package set.  (roshi, 16:16:46)

* (1207251) Fedup fail to decrypt disk  (roshi, 16:16:56)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1207251   (roshi,
16:16:57)
  * Proposed Blocker, fedup, NEW  (roshi, 16:16:57)
  * AGREED: - 1207251 - AcceptedBlocker Beta - This bug is a clear
violation of the following beta criterion: For each one of the
release-blocking package sets, it must be possible to successfully
complete an upgrade from a fully updated installation of the
previous stable Fedora release with that package set installed
(roshi, 16:19:55)

* (1206404) Crash on transition from g-i-s to GNOME on 'basic graphics'
  install (nomodeset)  (roshi, 16:20:09)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1206404   (roshi,
16:20:12)
  * Proposed Blocker, gdm, NEW  (roshi, 16:20:14)
  * AGREED: - 1206404 - RejectedBlocker AcceptedFreezeException Beta -
This bug doesn't quite violate the criterion (gdm/g-i-s runs, and a
user gets created) and appears to be only reproducible with a
specific setup. If this is found to be more widespread, please
repropose.  (roshi, 16:30:50)

* (1205534) gnome-initial-setup crashes upon selecting language  (roshi,
  16:31:08)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1205534   (roshi,
16:31:11)
  * Proposed Blocker, gnome-initial-setup, NEW  (roshi, 16:31:13)
  * AGREED: - 1105534 - Punt - We need more information about this bug
before we can determine it's blocker status.  (roshi, 16:35:48)

* (864198) grubby fatal error updating grub.cfg when /boot is btrfs
  (roshi, 16:36:02)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=864198   (roshi,
16:36:05)
  * Proposed Blocker, grubby, ASSIGNED  (roshi, 16:36:08)
  * AGREED: - 864198 - AcceptedBlocker Beta - This bug is a clear
violation of the criterion: The installed system must be able to
download and install updates with the default console package
manager. when /boot is on btrfs.  (roshi, 16:45:17)

* (1206394) Error: g-bd-md-error-quark: Failed to parse mdexamine data
  (0)  (roshi, 16:45:36)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1206394   (roshi,
16:45:39)
  * Proposed Blocker, libblockdev, MODIFIED  (roshi, 16:45:41)
  * AGREED: - 1206394 - AcceptedBlocker Beta - This bug is a clear
violation of the beta RAID criterion: The installer must be able to
detect and install to hardware or firmware RAID storage devices
(roshi, 16:49:49)

* (1200901) invisible mouse cursor in wayland login-screen when in VM
  (roshi, 16:50:14)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1200901   (roshi,
16:50:17)
  * Proposed Blocker, gdm, NEW  (roshi, 16:50:19)
  * 

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

2015-03-23 @ 1600 UTC ** Blocker Review Meeting Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 16:02:18 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-23/f22-blocker-review.2015-03-23-16.02.log.html
.

Meeting summary
---
* Roll Call  (roshi, 16:02:19)

* Introduction  (roshi, 16:03:35)
  * 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, 16:03:36)
  * We'll be following the process outlined at:  (roshi, 16:03:39)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 16:03:42)
  * The bugs up for review today are available at:  (roshi, 16:03:45)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
16:03:47)
  * The criteria for release blocking bugs can be found at:  (roshi,
16:03:49)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 16:03:52)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 16:03:55)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 16:03:58)

* (1160917) fedora-release-(product) conflicts when installing
  environment groups which specify a different product to the
  currently-installed one  (roshi, 16:05:17)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1160917   (roshi,
16:05:20)
  * Proposed Blocker, distribution, NEW  (roshi, 16:05:23)
  * LINK:

https://bugzilla.redhat.com/showdependencytree.cgi?id=1160917hide_resolved=1
(kparal, 16:08:43)
  * This bug (1160917) wasn't actually proposed as a blocker, skipping
(roshi, 16:19:33)

* (1204739) Installing Fedora Server netinst ends up with blocked
  Cockpit port  (roshi, 16:19:36)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1204739   (roshi,
16:19:39)
  * Proposed Blocker, fedora-release, ASSIGNED  (roshi, 16:19:43)
  * AGREED: - 1204739 - AcceptedBlocker Beta - This bug is a clear
violation of the criterion: After system installation without
explicit firewall configuration, the system firewall must be active
on all non-loopback interfaces. The only ports which may be open to
incoming traffic are port 22 (ssh), port 9090 (Cockpit web
interface)  (roshi, 16:27:34)

* (864198) grubby fatal error updating grub.cfg when /boot is btrfs
  (roshi, 16:27:59)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=864198   (roshi,
16:28:02)
  * Proposed Blocker, grubby, ASSIGNED  (roshi, 16:28:04)
  * LINK: https://github.com/rhinstaller/anaconda/pull/41 is the recent
pr for this  (adamw, 16:31:16)
  * AGREED: - 864198 - Punt - We're going to delay making a decision on
this bug until it can be clarified by the reporter as to what
exactly is desired.  (roshi, 16:42:14)

* (1204612) eth0 is going missing in the cloud images  (roshi, 16:42:17)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1204612   (roshi,
16:42:19)
  * Proposed Blocker, initscripts, NEW  (roshi, 16:42:22)
  * AGREED: - 1204612 - AcceptedBlocker Beta - This bug violates the
alpha criterion: The installed system must be able to download and
install updates with the default console package manager.  (roshi,
16:50:26)

* (1201897) SIGSEGV in libedit call in installer  (roshi, 16:50:36)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1201897   (roshi,
16:50:36)
  * Proposed Blocker, libedit, NEW  (roshi, 16:50:37)
  * AGREED: - 1201897 - AcceptedBlocker - This bug is a clear violation
of the following criterion: When using a dedicated installer image,
the installer must be able to complete an installation using the
text, graphical and VNC installation interfaces.  (roshi, 16:58:43)

* (1204031) 22 Beta TC3 install images do not bring up network (unless
  updates image or kickstart used)  (roshi, 16:58:59)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1204031   (roshi,
16:59:02)
  * Proposed Blocker, lorax, ON_QA  (roshi, 16:59:05)
  * AGREED: - 1204031 - AcceptedBlocker - This bug is a clear violation
of the following criterion: When using a release-blocking dedicated
installer image, the installer must be able to use either HTTP or
FTP repositories (or both) as package sources. Release-blocking
network install images must default to a valid publicly-accessible
package source.  (roshi, 17:04:13)

* (1201120) DeviceTreeError: could not find parent for subvol  (roshi,
  17:04:34)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1201120   (roshi,
17:04:37)
  * Proposed Blocker, python-blivet, ASSIGNED  (roshi, 17:04:40)
  * AGREED: - 1201120 - AcceptedBlocker Beta - This bug violates the
following criterion: When using the custom partitioning flow, the
installer must 

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

2015-03-09 @ 1600 UTC ** Blocker Review Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 16:05:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-09/f22-blocker-review.2015-03-09-16.05.log.html
.

Meeting summary
---
* Roll Call  (roshi, 16:05:02)

* Introduction  (roshi, 16:11:32)
  * 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, 16:11:32)
  * We'll be following the process outlined at:  (roshi, 16:11:36)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 16:11:38)
  * The bugs up for review today are available at:  (roshi, 16:11:41)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
16:11:43)
  * The criteria for release blocking bugs can be found at:  (roshi,
16:11:46)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 16:11:49)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 16:11:52)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 16:11:55)

* (1196397) FormatCreateError: ('invalid device specification',
  '/dev/mapper/VolGroup00-LogVol00')  (roshi, 16:13:07)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1196397   (roshi,
16:13:10)
  * Proposed Blocker, anaconda, NEW  (roshi, 16:13:13)
  * AGREED: - 1196397 - AcceptedBlocker Beta - This bug is a clear
violation of the Beta criterion: When using the custom partitioning
flow, the installer must be able to: Assign mount points to existing
storage volumes  (roshi, 16:18:36)

* (1197894) growpart: sfdisk dropped --show-pt-geometry option  (roshi,
  16:19:57)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1197894   (roshi,
16:20:00)
  * Proposed Blocker, cloud-utils, NEW  (roshi, 16:20:03)
  * AGREED: - 1197894 - AcceptedBlocker Beta - This bug is a clear
violation of the beta criterion: Release blocking cloud images must
be able to automatically utilize all available space on a supported
volume.  (roshi, 16:23:21)

* (1197380) Booting kvm guests hang on smpboot on kernel 4.0rc1 on AMD
  Athlon(tm) II P340 CPU  (roshi, 16:23:44)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1197380   (roshi,
16:23:47)
  * Proposed Blocker, kernel, NEW  (roshi, 16:23:50)
  * AGREED: - 1197380 - Punt - We don't have enough information about
how common this bug is so we're going to defer it until more testing
is done.  (roshi, 16:31:56)

* (1184173) dhclient fails to renew lease, results in dropped IPv4
  network connection  (roshi, 16:32:15)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1184173   (roshi,
16:32:18)
  * Proposed Blocker, bind, ASSIGNED  (roshi, 16:32:21)
  * AGREED: - 1184173 - AcceptedBlocker - This bug is a conditional
violation of the Alpha updates criterion: The installed system must
be able to download and install updates with the default console
package manager.  (roshi, 16:37:13)

* (1199270) Missing high contrast icons  (roshi, 16:37:55)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1199270   (roshi,
16:37:58)
  * Proposed Blocker, gnome-themes-standard, NEW  (roshi, 16:38:00)
  * AGREED: - 1199270 - AcceptedBlocker Final - This bug is a clear
violation of Final workstation requirements: All applications
installed by default in Fedora Workstation should have a high
contrast icon.  (roshi, 16:43:50)

* Open Floor  (roshi, 16:46:31)

Meeting ended at 16:48:35 UTC.

Action Items


Action Items, by person
---
* **UNASSIGNED**
  * (none)

People Present (lines said)
---
* roshi (82)
* adamw (22)
* jreznik (12)
* pschindl (10)
* tflink (9)
* kraulain (6)
* zodbot (3)
* kushal (1)
* randomuser (1)

Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

DNF Migration Tasks

[Mike Ruckman]

Greetings fellow testers! At the last QA meeting [0] we decided to break
the bits from the migration overview [1] into manageable chunks. So I
did that, and they live here [2] on our trac instance. If you have some
time, take a look at the tickets and assign it to yourself if you're so
inclined.

I just split out the relevant bits of the overview into tasks, and it
would be good to look over the resources we have for testing and mark
those in the ticket (that way others can help out with the ticket).

Let me know if you have any questions either here on the list or in the
#fedora-qa channel on freenode.

Thanks!

[0]
http://meetbot.fedoraproject.org/fedora-meeting/2015-03-02/fedora-qa.2015-03-02-16.00.html
[1]
https://lists.fedoraproject.org/pipermail/test/2015-February/125166.html
[2]
https://fedorahosted.org/fedora-qa/query?keywords=~dnf_migrationstatus=!closed

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Enlightenment default option with KDE Plasma

[Mike Ruckman]

On Tue, Mar 03, 2015 at 12:58:29PM +, Alexander Bisogianis wrote:
 Hi,
 
 I just installed the latest nightly alpha, selecting KDE Plasma as the 
 desktop.
 After installation, in KDM, for some reason Enlightenment is the default DE.
 
 Why is Enlightenment installed in the first place and why is it the default? 
 :)
 
 Abis.

Hey Alexander,

When you say nightly alpha which image do you mean? The current build
for testing the alpha release is TC8, which is found here [0]. From your
brief description, it sounds similar to this bug [1]. Could you give
some more details and perhaps comment in the bug if it seems relevant?

Once I know what image you used I'll try to reproduce and either get a
bug filed or comments submitted for an existing bug.

Thanks!

[0] http://dl.fedoraproject.org/pub/alt/stage/22_Alpha_TC8/
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1197135

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

2015-03-02 @ 1700 ** Blocker Review Meeting Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 17:16:09 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-02/f22-blocker-review.2015-03-02-17.16.log.html
.

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

* Introduction  (roshi, 17:18:16)
  * 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:18:16)
  * We'll be following the process outlined at:  (roshi, 17:18:20)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 17:18:23)
  * The bugs up for review today are available at:  (roshi, 17:18:25)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
17:18:28)
  * The criteria for release blocking bugs can be found at:  (roshi,
17:18:30)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 17:18:33)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 17:18:36)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 17:18:39)

* (1183807) network spoke listed as not connected despite having
  assigned IP and hostname  (roshi, 17:21:13)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1183807   (roshi,
17:21:16)
  * Proposed Blocker, anaconda, NEW  (roshi, 17:21:18)
  * AGREED: - 1183807 - AcceptedBlocker Alpha - This but is a clear
violation of the Alpha criterion: When using a dedicated installer
image, the installer must be able to complete an installation using
the text, graphical and VNC installation interfaces.  (roshi,
17:26:26)

* (1197290) realm crash during kickstart  (roshi, 17:26:35)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1197290   (roshi,
17:26:35)
  * Proposed Blocker, anaconda, POST  (roshi, 17:26:35)
  * AGREED: - 1197290 - AcceptedBlocker Alpha - This bug is a clear
violation of the Alpha criterion: It must be possible to join the
system to a FreeIPA or Active Directory domain at install time and
post-install, and the system must respect the identity,
authentication and access control configuration provided by the
domain.  (roshi, 17:34:03)

* realm crash during kickstart  (roshi, 17:34:21)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1197838   (roshi,
17:34:28)
  * Proposed blocker, sssd, NEW  (roshi, 17:34:53)
  * ACTION: roshi to file a ticket for the secretarializor badge
(roshi, 17:40:56)
  * ACTION: adamw to file a ticket for the secretarializer badge, and
fire roshi for spelling it wrong  (adamw, 17:41:28)
  * AGREED: - 1197838 - AcceptedBlocker Alpha - This bug is a clear
violation of the Alpha criterion: It must be possible to join the
system to a FreeIPA or Active Directory domain at install time and
post-install, and the system must respect the identity,
authentication and access control configuration provided by the
domain.  (roshi, 17:42:24)

* (1197218) - Add missing dependencies into freeipa packages  (roshi,
  17:45:46)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1197218   (roshi,
17:45:54)
  * Proposed Blocker, freeipa, ASSIGNED  (roshi, 17:46:08)
  * AGREED: - 1197218 - AcceptedBlocker Alpha - This bug is a clear
violation of the Alpha criterion: It must be possible to join the
system to a FreeIPA or Active Directory domain at install time and
post-install, and the system must respect the identity,
authentication and access control configuration provided by the
domain.  (roshi, 17:48:51)

* (1194682) Qt plugins fail to load or crash when built with gcc5
  (roshi, 17:48:57)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1194682   (roshi,
17:48:59)
  * Proposed Blocker, gcc, MODIFIED  (roshi, 17:49:02)
  * punting this to the end of blocker discussion  (roshi, 17:57:53)

* (1195485) cannot start user session (gdm returns back to the login
  page)  (roshi, 17:57:54)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1195485   (roshi,
17:57:57)
  * Proposed Blocker, gdm, NEW  (roshi, 17:58:00)
  * AGREED: - 1195485 - RejectedBlocker Alpha - This bug doesn't seem to
be reproducible. If more information comes to the surface, please
repropose with steps to reproduce.  (roshi, 18:11:15)

* (1197224) System sometimes gets stuck during gdm init when autologin
  is enabled (e.g. live images)  (roshi, 18:11:25)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1197224   (roshi,
18:11:28)
  * Proposed Blocker, gdm, ON_QA  (roshi, 18:11:30)
  * AGREED: - 1197224 - AcceptedBlocker Alpha - This bug is a
conditional violation of the following alpha criterion:
Release-blocking live images must boot to the expected boot 

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

DNF Migration testing overview

[Mike Ruckman]

Greetings Testers!

With the F22 switch from yum to dnf as a package manager, there was a need to
figure out what the scope would be for QA testing. Naturally, to define the
scope for a subset, I had to figure out (at least in a general sense) how
large the complete set is. There's a multitude of complication vectors with a
switch like this - especially since dnf is specifically designed to not be a
drop in replacement for yum.

First question: Who/what all uses yum?
--

Swapping out yum is the equivalent of someone coming up with a new form of
hemoglobin, then trying to figure out what all could go wrong when you make
the swap (tl;dr: Everything). The first to come to mind is anyone who installs
packages from the CLI. But then you have all the GUI front-ends (PackageKit
and Apper) and all the build tools - not to mention the installer.

Some places yum touches:
 - Oz/ImageFactory (Building Cloud images)
 - koji (RPM-based build system)
 - pungi (Build installation trees and isos)
 - ABRT (Automatic Bug Reporting Tool)
 - Anaconda (Fedora installer)
 - liveimage-creator (tool for creating live images)
 - cloud-init (tool for configuring freshly launched cloud images)
 - FedUp (tool for updating Fedora between releases)
 - Software Center and Apper (Default software installers)
 - rolekit (tool to easily deploy roles to a Server installation)
 - virt-builder and friends (tools for manipulating virtualized environments)

All of those make up a large portion of the Fedora ecosystem - everything from
composing images to users being able to update their software packages, and
this doesn't even touch the different ways each of the above actually *uses*
yum functionality - just that yum somehow impacts these tools.

Second question: What's QA responsible for?
---

According to the QA wiki page: Fedora QA is the project which covers all
testing of the software that makes up Fedora. It's our goal to continually
improve the quality of Fedora releases and updates. A more literal translation
of that passage would indicate that QA is responsible for all the testing, but
a more nuanced interpretation says that QA is responsible for releases and
updates to those releases. Luckily for us in QA, we seem to operate from the
more nuanced interpretation.

So, out of that list above, which things would QA need to test?
 - Anaconda (which we already test heavily)
 - ABRT
 - FedUp
 - Software Center/Apper
 - rolekit

While those are the things easily placed directly under QA for testing, other
teams would likely appreciate help in testing their tools. This doesn't
necessarily equate to more work for QA, since a lot of the feedback the other
teams (Release Engineering, Infra) get is from QA testing the output their
tools create - releases and updates.

Also, those 5 things aren't trivial to test either. Here's the partial
breakdown:

Anaconda:
 - GUI installation
   - Do all the offered mechanisms work?
 - Package selection (installing all the packages selected)
 - Remote repositories
 - text based installation
 - kickstart installation
   - This is non-trivial to test

ABRT:
 This tool uses a bunch of yum tricks and workarounds to get the needed
 information (AIUI)
 - We have 36 testcases for this (some will need updated)

FedUp:
 - F20-F22 upgrades
 - How to handle migrating existing systems from yum to dnf. Each will have
   different installed package sets due to utilizing different depsolvers.
 - This will require more testing during the F23 cycle than during the F22
   cycle

Software Center and Apper:
 These tools aren't just a front-end for yum/dnf, but tie into the libraries
 dnf uses. For the switch to dnf, this is hawkey and libsolv. It could be
 argued that this doesn't need to be tested as part of the migration, but they
 for sure fall under the Default application functionality Final criterion.

rolekit:
 We get a small pass for this one, since there's currently only two supported
 roles: Domain Controller and Database. rolekit relies on yum for installing
 package sets for the role, so it'll have to be ported and tested. Hopefully
 this requires minimal extra testing.

Third question: What do we currently have to work with?
---

Our wiki has a plethora of testcases and documentation we can utilize
throughout this transition. We should be able to use/re-purpose large portions
of our existing testcases to get good test coverage of the change. We might
also have to take a look at the Release criteria going forward to make sure
there aren't any yum-isms left over. All this means is that we don't have to
start from scratch when it comes to testing this.

Testcases:

  I count 54 testcases currently available to test ABRT, FedUp, Yum,
  Installation Repos, and kickstarts. Many of these will likely need revised
  and more will likely need added to get the coverage we need.

Matrix Changes:

  For the image 

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

2015-02-16 @ 1700 UTC ** Blocker Review Meeting Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 17:30:53 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-02-16/f22-blocker-review.2015-02-16-17.30.log.html
.

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

* Introduction  (roshi, 17:34:31)
  * 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:34:32)
  * We'll be following the process outlined at:  (roshi, 17:34:36)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 17:34:38)
  * The bugs up for review today are available at:  (roshi, 17:34:41)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
17:34:43)
  * The criteria for release blocking bugs can be found at:  (roshi,
17:34:46)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 17:34:48)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 17:34:51)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 17:34:54)

* (1192702) ImportError: cannot import name storageInitialize  (roshi,
  17:35:09)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1192702   (roshi,
17:35:12)
  * Proposed Blocker, anaconda, MODIFIED  (roshi, 17:35:15)
  * AGREED: - 1192702 - AcceptedBlocker Alpha - This bug is a clear
violation of the Alpha criterion: The installer must run when
launched normally from the release-blocking images  (roshi,
17:39:16)

* (1190610) imsettings NVR is lower in rawhide/F22  (roshi, 17:40:15)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1190610   (roshi,
17:40:16)
  * Proposed Blocker, imsettings, NEW  (roshi, 17:40:16)

* (1191171) Could not sync environment to dbus. (startkde)  (roshi,
  17:42:20)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1191171   (roshi,
17:42:20)
  * Proposed Blocker, plasma-workspace, NEW  (roshi, 17:42:20)
  * AGREED: - 1191171 - AcceptedBlocker Alpha - This bug is a clear
violation of the Alpha criterion: A system installed with a
release-blocking desktop must boot to a log in screen where it is
possible to log in to a working desktop using a user account created
during installation or a 'first boot' utility.  (roshi, 17:45:54)
  * ACTION: roshi to test 1191171 in a VM  (roshi, 17:47:45)

* (1192259) Anaconda text install doesn't update spoke status  (roshi,
  17:48:12)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1192259   (roshi,
17:48:15)
  * Proposed Blocker, anaconda, NEW  (roshi, 17:48:17)
  * AGREED: - 1192259 - AcceptedBlocker Final - This bug is a clear
violation of the Final criterion: The installer must be able to
complete an installation using all supported interfaces.  (roshi,
17:52:22)

* (1190377) SELinux is preventing polkitd from 'read' accesses on the
  lnk_file localtime.  (roshi, 17:52:31)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1190377   (roshi,
17:52:34)
  * Proposed Blocker, selinux-policy, NEW  (roshi, 17:52:37)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1190377#c2
(danofsatx, 17:52:59)

* Open Floor  (roshi, 17:54:03)

Meeting ended at 17:58:56 UTC.

Action Items

* roshi to test 1191171 in a VM

Action Items, by person
---
* roshi
  * roshi to test 1191171 in a VM
* **UNASSIGNED**
  * (none)

People Present (lines said)
---
* roshi (86)
* kparal (22)
* danofsatx (21)
* Corey84 (16)
* adamw (15)
* zodbot (5)
* pschindl (4)

Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Release criteria notes

[Mike Ruckman]

On Thu, Feb 05, 2015 at 03:21:53PM -0800, Adam Williamson wrote:
 On Thu, 2015-02-05 at 11:24 -0700, Mike Ruckman wrote:
  Greetings testers!
  
  While looking into the affects of the yum/dnf migration I noticed 
  some cleanup
  opportunities with the release criteria and thought I'd email the 
  list before
  making any changes.
  
  Beta
  
  
  Package set selection
  
Should we update this to say when using any network install 
  image...
instead of when using the generic? I'd add a note with something 
  like,
[Any?] This means any of the productized network installation 
  media and
the base network installation image.
 
 No. I only just wrote this, and it's specifically this way for a 
 reason. We're getting the generic netinst back for F22, and we only 
 want to 'officially support' package set selection when using that 
 image. The Product-ized netinsts are only 'officially supported' for 
 deploying their own package sets. At least, that's the current plan.

Ah, ok. I must've have missed that. So will the prodcutized netinsts not
even offer other package sets?

  
  Kickstart Delivery
  
Not really a criterion change, but we still list a diskette as a 
  supported
delivery mechanism [0]. Should we remove this, or do we still 
  actively test
using a diskette for ks delivery?
 
 Hum, not sure. I know I haven't had a floppy drive for like ten years 
 so it might be hard to test, but people do do a lot of really weird 
 stuff.

I think I might have a disk drive around here somewhere, but I don't
have disks any more (not even to use for coasters)...

  Updgrade Requirements
  
This currently reads: The release-blocking package sets are the 
  minimal set,
and the sets for each one of the release-blocking desktops.
  
Should this be updated to each one of the release-blocking 
  products and
release-blocking desktops?
 
 Probably, yeah. It's a bit wiggly either way, but I like that one 
 better...
 
  Domain controller role
  
The note says this criteria should be removed after F21 - but 
  since rolekit
relies on yum to install the bits needed for the domain 
  controller, should
we keep this in place for F22 through the dnf migration?
 
 It's supposed to be *moved* to a separate page, not just removed. I've 
 had that proposal in draft for a while now, I should probably just go 
 ahead and do it:
 
 https://lists.fedoraproject.org/pipermail/server/2015-January/001719.html
 

Ah, that makes sense. I just wasn't sure from the wording on the
criteria pages themselves.

  Cloud-init
  
This was an oversight on my part originally. We need to define the 
  specific
bits of cloud-init that need to work. It'd be nice and easy to 
  just say,
all of them, but cloud-init has a yum module and no dnf module. 
  We need
to figure out what to do about cloud-init if dnf support won't be 
  added.
 
 And by 'we', we mean 'you' ;)

Yeah, already working on it with gholms. I'll work through it with the
Cloud WG.

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Release criteria notes

[Mike Ruckman]

On Fri, Feb 06, 2015 at 01:38:55PM +0530, Sudhir Dharanendraiah wrote:
 
 On 02/06/2015 04:51 AM, Adam Williamson wrote:
 Kickstart Delivery
 
Not really a criterion change, but we still list a diskette as a
 supported
delivery mechanism [0]. Should we remove this, or do we still
 actively test
using a diskette for ks delivery?
 Hum, not sure. I know I haven't had a floppy drive for like ten years
 so it might be hard to test, but people do do a lot of really weird
 stuff.
 
 Just a thought. We might want to have 'phase out' section and put last
 supported release and phase it out in next release. If it generates enough
 noise, we can move it back to main criteria.
 
 Regards,
 Sudhir
 

That sounds like a good idea to me. Do we have a phase out SOP
somewhere for criteria? I'm not finding it readily on the wiki if it's
there.

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Release criteria notes

[Mike Ruckman]

Greetings testers!

While looking into the affects of the yum/dnf migration I noticed some cleanup
opportunities with the release criteria and thought I'd email the list before
making any changes.

Beta


Package set selection

  Should we update this to say when using any network install image...
  instead of when using the generic? I'd add a note with something like,
  [Any?] This means any of the productized network installation media and
  the base network installation image.

Kickstart Delivery

  Not really a criterion change, but we still list a diskette as a supported
  delivery mechanism [0]. Should we remove this, or do we still actively test
  using a diskette for ks delivery?

Updgrade Requirements

  This currently reads: The release-blocking package sets are the minimal set,
  and the sets for each one of the release-blocking desktops.

  Should this be updated to each one of the release-blocking products and 
  release-blocking desktops?

Domain controller role

  The note says this criteria should be removed after F21 - but since rolekit
  relies on yum to install the bits needed for the domain controller, should
  we keep this in place for F22 through the dnf migration?

Cloud-init

  This was an oversight on my part originally. We need to define the specific
  bits of cloud-init that need to work. It'd be nice and easy to just say, 
  all of them, but cloud-init has a yum module and no dnf module. We need
  to figure out what to do about cloud-init if dnf support won't be added.

Role installation

  For at least F22, do we need to have a criterion for installing new roles
  with rolekit? Or will brought to a working configuration cover this enough?

Final
=

Domain controller role

  As with the beta, I'd suggest we keep this through F22 to make sure things
  work.

I know herding the Release Criteria is typically an Adam thing, but thought
I'd go ahead and ping the list with these small bits.

Thoughts?

[0] 
http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_6._Making_the_Kickstart_File_Available

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

2015-02-02 @ 1700 UTC ** Blocker Review Meeting Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 17:06:14 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-02-02/f22-blocker-review.2015-02-02-17.06.log.html
.

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

* Introduction  (roshi, 17:09:07)
  * 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:09:08)
  * We'll be following the process outlined at:  (roshi, 17:09:12)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 17:09:14)
  * The bugs up for review today are available at:  (roshi, 17:09:17)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
17:09:19)
  * The criteria for release blocking bugs can be found at:  (roshi,
17:09:22)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 17:09:24)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 17:09:27)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 17:09:30)

* (1185999) [Gtk3] Text on various bits of chrome (tab titles, menus,
  buttons...) is white with GTK+ 3.15.4  (roshi, 17:09:49)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1185999   (roshi,
17:09:52)
  * Proposed Blocker, gtk3, NEW  (roshi, 17:09:55)
  * AGREED: - 1185999 - AcceptedBlocker Final - This bug is a
conditional violation of the Alpha criterion, It must be possible
to run the default web browser and a terminal application from all
release-blocking desktop environments... but isn't deemed bad
enough to block until a later Milestone as FF *technically* works.
(roshi, 17:31:11)

* (1187742) rebuild openldap with support for moznss  (roshi, 17:32:05)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1187742   (roshi,
17:32:06)
  * Proposed Blocker, openldap, NEW  (roshi, 17:32:06)
  * LINK:
http://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Roles
(roshi, 17:36:09)
  * AGREED: - 1187742 - AcceptedBlocker Beta - This bug is a clear
violation of the Beta criterion: Release-blocking roles and the
supported role configuration interfaces must meet the core
functional Role Definition Requirements...  (roshi, 17:39:35)

* Discussion Time  (roshi, 17:40:17)
  * Last working boot.iso is the currently nominated nightly. Live
images have more recent images to test  (roshi, 18:03:27)
  * LINK:

https://lists.fedoraproject.org/pipermail/devel-announce/2015-February/001530.html
(danofsatx, 18:07:11)

Meeting ended at 18:10:22 UTC.

Action Items


Action Items, by person
---
* **UNASSIGNED**
  * (none)

People Present (lines said)
---
* roshi (120)
* adamw (64)
* kparal (43)
* danofsatx (27)
* pschindl (12)
* zodbot (5)
* nirik (4)

Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

Re: Self-introduction: Abdelhak BOUGOUFFA

[Mike Ruckman]

On Wed, Jan 28, 2015 at 11:37:56PM +0100, Abdelhak Bougouffa wrote:
 Hi,
 
 My name is Abdelhak BOUGOUFFA, I'm from Algeria
 I'm a student in InfoTronics field (Informatics and Electronics), I'm a
 C, Python, PHP, JavaScript developer
 
 I'm also a skilled GNU/Linux administrator, I think that I can join the
 QA team to test the fresh packages, report bugs and even; debug them :-D
 
 Have good day :)

Hey Abdelhak,

Welcome to QA! It's good to have you aboard! Since you've sent the
introduction email to the list, I presume you've read the Join [0] page
on the wiki. Also, you have some python skills, so you might also be
interested in some of the qa-devel work, like blockerbugs [1] or
taskotron [2] as well.

Looking forward to working with you! Drop by #fedora-qa on freenode
sometime and say hey!

[0] https://fedoraproject.org/wiki/QA/Join
[1] https://qa.fedoraproject.org/blockerbugs/
[2] https://fedoraproject.org/wiki/Taskotron

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

2015-01-26 @ 1700 UTC ** Blocker Review Meeting Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 17:00:18 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-26/f22-blocker-review.2015-01-26-17.00.log.html
.


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

* Introduction  (roshi, 17:02:32)
  * 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:32)
  * We'll be following the process outlined at:  (roshi, 17:02:36)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 17:02:39)
  * The bugs up for review today are available at:  (roshi, 17:02:41)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
17:02:44)
  * The criteria for release blocking bugs can be found at:  (roshi,
17:02:46)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 17:02:49)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 17:02:52)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 17:02:55)

* (1184453) mouse cursor is invisible for 1 minute after log in, g-s-d
  seems to be stuck waiting for cups  (roshi, 17:04:14)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1184453   (roshi,
17:04:17)
  * Proposed Blocker, cups, NEW  (roshi, 17:04:19)
  * AGREED: - 1184453 - AcceptedBlocker for Beta - This bug
conditionally violates the Alpha criterion It must be possible to
run the default web browser and a terminal application from all
release-blocking desktop environments. by making it
difficult/impossible to do anything within the GUI, the violation is
considered serious enough to block Beta but not Alpha  (adamw,
17:14:51)
  * LINK:
https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting#Secretary_Duty
(roshi, 17:19:06)

* (1185195) SELinux is preventing NetworkManager from 'create' accesses
  on the lnk_file .resolv.conf.NetworkManager.  (roshi, 17:19:45)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1185195   (roshi,
17:19:48)
  * Proposed Blocker, selinux-policy, NEW  (roshi, 17:19:51)
  * AGREED: - 1185195 - AcceptedBlocker - This bug prevents anything
requiring the network from working. Violates at least the following
criterion: The installed system must be able to download and
install updates with the default console package manager.  (roshi,
17:23:11)

* (1184933) login screen stuck after switching users  (roshi, 17:23:32)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1184933   (roshi,
17:23:32)
  * Proposed Blocker, gdm, MODIFIED  (roshi, 17:23:32)
  * ACTION: kparal to propose criteria change to the list regarding user
switching  (roshi, 17:34:57)
  * AGREED: - 1184933 - AcceptedBlocker - This bug is a conditional
violation of the criterion: Shutting down, logging out and
rebooting must work using standard console commands and the
mechanisms offered (if any) by all release-blocking desktops. As
Switch User is an offered mechanism.  (roshi, 17:36:03)

* (1185117) UEFI dual-boot + Windows, cannot practically remove and
  install Fedora over an existing default opensuse installation  (roshi,
  17:36:08)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1185117   (roshi,
17:36:11)
  * Proposed Blocker, anaconda, NEW  (roshi, 17:36:14)
  * AGREED: - 1185117 - AcceptedBlocker for Beta - This bug is a
violation of the Beta criterion: Correctly interpret, and modify as
described below, any disk with a valid ms-dos or gpt disk label and
partition table containing ext4 partitions, LVM and/or btrfs
volumes...  (roshi, 17:45:18)

* (1182652) Missing high contrast icon  (roshi, 17:45:57)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1182652   (roshi,
17:45:57)
  * Proposed Blocker, setroubleshoot, NEW  (roshi, 17:45:57)
  * AGREED: - 1182652 - AcceptedBlocker - This bug violates the
criterion: All applications installed by default in Fedora
Workstation must comply with each MUST and MUST NOT guideline in the
Applications and Launchers policy.  (roshi, 17:49:40)

* Open Floor  (roshi, 17:49:49)

Meeting ended at 17:58:54 UTC.

Action Items

* kparal to propose criteria change to the list regarding user switching

Action Items, by person
---
* kparal
  * kparal to propose criteria change to the list regarding user
switching
* **UNASSIGNED**
  * (none)

People Present (lines said)
---
* roshi (114)
* adamw (82)
* kparal (38)
* danofsatx (27)
* pschindl (8)
* zodbot (4)
* tonghuix (4)
* oddshocks (1)

Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Release criterion proposal: Package sets (Alpha and Beta)

[Mike Ruckman]

On Thu, Jan 22, 2015 at 04:20:48PM -0800, Adam Williamson wrote:
 
 Hum, so thinking about it a bit further, I'd like to add one more 
 thing to this proposal.
 
 
 On reflection I think we *should* require install of release blocking 
 desktops and minimal package set to work with the frozen release 
 package set, because I can see cases where it would be important to be 
 able to fire off an install and be 100% confident you're not going to 
 have package set issues; people may want to use the frozen repo for 
 that purpose, so they're sure updates won't introduce any new problems.
 
 We also seem to be pretty much committed to still having the universal 
 network install image, now - at least for F22.
 
 So, to cover those goals, propose we basically move the existing Alpha 
 criterion to Final, with a tweak to refer to the network install image 
 and the frozen repos specifically:
 
 When installing with the network install image with no update 
 repositories enabled, the installer must be able to install each of 
 the release blocking desktops, as well as the minimal package set.
 -- 
 Adam Williamson
 Fedora QA Community Monkey
 IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
 http://www.happyassassin.net

Just to sum it up for people, the proposal overall is:

 - Reword the alpha criterion [0]
 - add a Beta criterion (with the latest extension) [1]
 - add a net-install Final criterion [2]

I don't see anything worrisome about any of these changes. Gives us
good, well defined areas we know we want covered.

--

[0] When installing with a release-blocking dedicated installer image, the
installer must be able to install the default package set.

[1] When installing with a release-blocking dedicated installer image, the
default package set must be correct, and choosing a different package set must
work.

[2] When installing with the network install image with no update repositories
enabled, the installer must be able to install each of the release blocking
desktops, as well as the minimal package set.

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Release criterion proposal: Package sets (Alpha and Beta)

[Mike Ruckman]

On Tue, Jan 20, 2015 at 12:46:34PM -0800, Adam Williamson wrote:
 Here's a ping on this (as I only got feedback from Mike before - 
 anyone else?) and a modification: I'd like to extend the Beta 
 criterion to read:
 
 When installing with a release-blocking dedicated installer image, 
 the default package set must be correct, and choosing a different 
 package set must work.
 
 with a footnote something like:
 
 'work' means that the package set selection mechanism itself must 
 work; when used, the packages that form the chosen set must actually 
 be the ones marked for installation. Package issues that render one or 
 more selectable package sets un-installable do not constitute a 
 violation of this criterion, though they may be violations of other 
 criteria.
 
 this is to cover things like 
 https://bugzilla.redhat.com/show_bug.cgi?id=1179362 , which I noticed 
 when filing it is a bit of a loophole in the proposed criteria.
 
 Any more thoughts, folks? Thanks!
 -- 
 Adam Williamson
 Fedora QA Community Monkey
 IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
 http://www.happyassassin.net

That addition to the proposed criteria sounds good to me. The definition
of 'work' makes sense as well.

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

2015-01-12 @ 1700 UTC ** Fedora Blocker Review Minutes

[Mike Ruckman]

I filled in a gap that zodbot missed when it died in the middle of the
meeting, but these should be complete.

==
#fedora-blocker-review: F22-blocker-review
==

Meeting started by roshi at 16:06:42 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-12/f22-blocker-review.2015-01-12-16.06.log.html
.

Meeting summary
---
* Roll Call  (roshi, 16:06:43)

* Introduction  (roshi, 16:08:49)
  * 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, 16:08:49)
  * We'll be following the process outlined at:  (roshi, 16:08:53)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 16:08:55)
  * The bugs up for review today are available at:  (roshi, 16:08:58)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
16:09:00)
  * The criteria for release blocking bugs can be found at:  (roshi,
16:09:03)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 16:09:05)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 16:09:08)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 16:09:11)

* (1166598) going back to installation destination picker swaps
  partitions on disks  (roshi, 16:09:36)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1166598   (roshi,
16:09:39)
  * Proposed Blocker, anaconda, ASSIGNED  (roshi, 16:09:42)
  * LINK:

http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-07/f22-blocker-review.2015-01-07-16.02.log.html
(roshi, 16:13:02)
  * AGREED: - 1166598 - AcceptedBlocker - This bug violates the beta
criterion Complete an installation using any combination of disk
configuration options it allows the user to select in the case you
change your mind  (roshi, 16:30:40)

* (1179905) [dnf] select default optional addons when changing
  environments  (roshi, 16:32:46)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1179905   (roshi,
16:32:49)
  * Proposed Blocker, anaconda, MODIFIED  (roshi, 16:32:52)
  * AGREED: - 1179905 - RejectedBlocker - This bug doesn't violate any
criterion we have currently and none of the release blocking package
sets use default option groups.

* (1180706) Does not launch: Gjs-CRITICAL **: Attempting to call back
  into JSAPI during the sweeping phase of GC.  (adamw, 16:46:29)
  * AGREED: - 1180706 - AcceptedBlocker - This bug is a clear violation
of the Final criterion: All applications that can be launched using
the standard graphical mechanism of a release-blocking desktop after
a default installation of that desktop must start successfully and
withstand a basic functionality test.  (adamw, 16:46:39)

* Open Floor  (adamw, 16:46:47)

Meeting ended at 16:48:30 UTC.


Action Items


Action Items, by person
---
* **UNASSIGNED**
  * (none)

People Present (lines said)
---
* roshi (70)
* adamw (35)
* kparal (24)
* brunowolff (5)
* zodbot (4)
* pschindl_wifi (3)
* jsmith (3)
* sgallagh (2)
* satellit (2)
* satellit_e (1)

Generated by `MeetBot`_ 0.1.4 - Edited by Roshi 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Proposal to CANCEL: 2015-01-12 Fedora QA Meeting

[Mike Ruckman]

On Sun, Jan 11, 2015 at 10:25:00AM -0800, Adam Williamson wrote:
 Hi folks! So I don't think we have anything particular to discuss at a 
 meeting tomorrow, thus according to the policy of not wasting people's 
 time with unnecessary meetings, I propose we cancel it. If anyone did 
 have something to discuss, please do reply to this mail!
 
 We could possibly move blocker review up by one hour to help out 
 European folks, but it may be a bit late for that.
 -- 
 adamw

We can just see how many people happen to be on IRC and get started
early - with the caveat that we can revisit bugs if developers or
packagers show up at the allotted time with info on a bug.

That work?

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

2014-01-07 @ 1600 ** Fedora Blocker Review Minutes

[Mike Ruckman]

==
#fedora-blocker-review: F22-blocker-review
==


Meeting started by roshi at 16:02:15 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-07/f22-blocker-review.2015-01-07-16.02.log.html
.

Meeting summary
---
* Roll Call  (roshi, 16:02:16)

* Change blocker review time discussion  (roshi, 16:05:41)
  * AGREED: Hold next blocker review on Monday 2014-01-12  (roshi,
16:12:36)

* Introduction  (roshi, 16:14:27)
  * 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, 16:14:28)
  * We'll be following the process outlined at:  (roshi, 16:14:31)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(roshi, 16:14:34)
  * The bugs up for review today are available at:  (roshi, 16:14:36)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (roshi,
16:14:39)
  * The criteria for release blocking bugs can be found at:  (roshi,
16:14:41)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
(roshi, 16:14:44)
  * LINK: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
(roshi, 16:14:47)
  * LINK:
https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
(roshi, 16:14:50)

* (1169019) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in
  position 11: ordinal not in range(128)  (roshi, 16:15:07)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1169019   (roshi,
16:15:10)
  * Proposed Blocker, anaconda, ASSIGNED  (roshi, 16:15:13)
  * AGREED: - 1169019 - AcceptedBlocker - This bug is a conditional
violation of the Alpha criterion: The installer must be able to
complete an installation to a single disk using automatic
partitioning.  (roshi, 16:27:01)

* (1179362) boot.iso installs result in console login  (roshi, 16:30:55)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1179362   (roshi,
16:30:55)
  * Proposed Blocker, anaconda, ASSIGNED  (roshi, 16:30:56)
  * AGREED: - 1179362 - AcceptedBlocker - This bug is a clear violation
of the Alpha Package Sets criterion: When doing a graphical install
using the dedicated installer images, the installer must be able to
install each of the release blocking desktops, as well as the
minimal package set.  (roshi, 16:35:49)

* (1170803) calls e2fsck on all ext volumes, provides no status
  indicator, and hangs indefinitely if e2fsck doesn't exit  (roshi,
  16:36:05)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1170803   (roshi,
16:36:08)
  * Proposed Blocker, e2fsprogs, NEW  (roshi, 16:36:11)
  * AGREED: - 1170803 - RejectedBlocker - This bug doesn't clearly
violate any criteria and looks to be getting worked on either way.
Please repropose if it's found to violate another criterion.
(roshi, 16:54:50)
  * LINK:

http://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Initialization_requirements
(roshi, 16:55:24)

* (1166598) going back to installation destination picker swaps
  partitions on disks  (roshi, 16:55:37)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1166598   (roshi,
16:55:40)
  * Proposed Blocker, anaconda, ASSIGNED  (roshi, 16:55:42)
  * LINK: http://plantpoweredkitchen.com/recipes/recipe-mac-oh-geez/
(danofsatx|w, 17:01:11)
  * AGREED: - 1166598 - Punt - It's not clear where this bug or the fix
currently stands. Punting until we have more information.  (roshi,
17:12:00)

* (1177988) ConfigError: Repository updates has no mirror or baseurl
  set.  (roshi, 17:12:08)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1177988   (roshi,
17:12:11)
  * Proposed Blocker, anaconda, ASSIGNED  (roshi, 17:12:14)
  * AGREED: - 1177988 - AcceptedBlocker - This bug violates the Beta
criterion: The installer must be able to complete a scripted
installation which duplicates the default interactive installation
as closely as possible.  (roshi, 17:20:55)

* (1170800) Please stop overwriting anaconda's stylesheet  (roshi,
  17:20:59)
  * Proposed Blocker, fedora-productimg-server, NEW  (roshi, 17:21:00)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1170800   (roshi,
17:21:02)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1176411   (adamw,
17:23:33)
  * AGREED: - 1170800 - AcceptedBlocker - This bug breaks keyboard usage
for installation, and thus is a conditional violation of the
following Final criterion: Installer must be able to complete an
installation.  (roshi, 17:29:56)

* (1170788) [abrt] gnome-shell: check_fontmap_changed(): gnome-shell
  killed by SIGSEGV  (roshi, 17:30:01)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1170788   (roshi,
17:30:04)
  * Proposed Blocker, gnome-shell, NEW  (roshi, 

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

[Mike Ruckman]

On Tue, Jan 06, 2015 at 04:10:39AM -0500, Kamil Paral wrote:
  # 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!
 
 I added the meetings to our QA calendar:
 https://apps.fedoraproject.org/calendar/QA/

Thanks!

 
 Anyone can add this calendar to his or her calendar application by using this 
 iCal link:
 https://apps.fedoraproject.org/calendar/ical/QA/
 
 And due to this, I realized I can't attend these meetings until Feb 11, it 
 collides with my other activities.
 
 So, either you need to get by without me (no hurt feelings here;)), or we 
 need to reschedule it to a different day. I talked to Petr and Mondays after 
 the regular QA meeting (17:00-20:00 UTC) would be fine for us, it would be 
 just a single evening occupied instead of two evenings taken per week. For US 
 people, it would be one hour later, which is also a benefit.

I think that could work fine (for me at least) - perhaps we can test it
out next week? Or throw the idea on the QA meeting agenda if there isn't
enough response here on list?

--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[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
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Self-introduction: Carlos Morel-Riquelme

[Mike Ruckman]

On Mon, Dec 22, 2014 at 03:57:05PM -0300, Carlos Morel-Riquelme wrote:
 Hello folks
 
 My name is Carlos Morel-Riquelme i'm from Chile and i'm contributor for
 Fedora Project since F20 in Testing ( Bodhi ) though i start using Fedora
 since F15, also i'm student of computer engineering and i have a little
 knowledge in Ruby and GTK+ .
 
 Well for finish i want say that i really apreciate the good enery and
 gratitude of Fedora team for my participation in F21 testing, read my name
 in the heroes of fedora is great :)
 
 
 Thank a lot
 
 http://fedoramagazine.org/heroes-of-fedora-qa-fedora-21-part-2/
 https://fedoraproject.org/wiki/User:Empateinfinito

Glad to have you aboard Carlos! Looking forward to seeing more of you in
the Heroes of Fedora :) Welcome to QA!

-- 
// Mike 
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test