DevHeads.net

Postings by Adam Williamson

Fedora 27 Final blocker status mail #1

Hi folks! As we're now frozen for Final, here's an update on blocker
bug status.

tl;dr action summary
====================

Accepted blockers
1. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1164492" title="https://bugzilla.redhat.com/show_bug.cgi?id=1164492">https://bugzilla.redhat.com/show_bug.cgi?id=1164492</a>
ACTION: desktop team to make change and submit update

2. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1486002" title="https://bugzilla.redhat.com/show_bug.cgi?id=1486002">https://bugzilla.redhat.com/show_bug.cgi?id=1486002</a>
ACTION: Konrad and pjones to continue collaborating and ship a fix

3. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1491320" title="https://bugzilla.redhat.com/show_bug.cgi?id=1491320">https://bugzilla.redhat.com/show_bug.cgi?id=1491320</a>
ACTION: kernel team to ship official update with fix, QA to test it

4.

Proposal to CANCEL: 2017-10-16 blocker review meeting

Hi folks! I'm proposing we cancel the blocker review meeting for
Monday, as there are no proposed Final (or Server Beta) blockers.
Thanks!

2017-10-16 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-10-16
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's time for another meeting! Let's call this the Everyone Tell Adam
What's Going On meeting, as I'm trying to catch up on return from
vacation :)

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2.

Interdependent packages *must* go in the same update - a reminder (ref. nss and nspr)

There are currently separate updates for nss 3.33.0 and nspr 4.17.0 in
both Fedora 26 and 27. However, nss 3.33.0 requires nspr 4.17.0.

As a reminder, this is a violation of the Updates Policy:

<a href="https://fedoraproject.org/wiki/Updates_Policy#Updating_inter-dependent_packages" title="https://fedoraproject.org/wiki/Updates_Policy#Updating_inter-dependent_packages">https://fedoraproject.org/wiki/Updates_Policy#Updating_inter-dependent_p...</a>

"When one updated package requires another (or more than one other),
the packages should be submitted together as a single update."

The problem with doing things this way is that, if the nss update
happened to be pushed stable before the nspr update (which could easily
happen due to human error, network issues etc.

Fedora 27 Beta blocker status mail #1

Hi folks! Time for an update on the Fedora 27 Beta status.

tl;dr action summary
====================

Accepted blockers
1. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1489164" title="https://bugzilla.redhat.com/show_bug.cgi?id=1489164">https://bugzilla.redhat.com/show_bug.cgi?id=1489164</a>
ACTION: QA to test and karma update:
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-fee0766883" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-fee0766883">https://bodhi.fedoraproject.org/updates/FEDORA-2017-fee0766883</a>
then check whether backgrounds are fixed for all blocking desktops
after compose run with update included.

2. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1487867" title="https://bugzilla.redhat.com/show_bug.cgi?id=1487867">https://bugzilla.redhat.com/show_bug.cgi?id=1487867</a>
ACTION: QA to test and karma update:
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-a8b4e05ef3" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-a8b4e05ef3">https://bodhi.fedoraproject.org/updates/FEDORA-2017-a8b4e05ef3</a>

3.

Proposal to CANCEL: 2017-09-11 Fedora QA Meeting (and blocker review meeting)

Hi folks! I'm proposing we cancel the QA meeting tomorrow. There's
nothing urgent to discuss that I'm aware of, and the focus for this
coming week will likely be Beta validation testing. There *will* be a
blocker review meeting at 1600 in #fedora-blocker-review, so please
come along to that if you can. Thanks!

Fedora 27 update karma requests

Hi folks! It's that time again when I ask for folks to test updates
that fix F27 blocker and freeze exception bugs, and provide karma
(feedback) in Bodhi.

2017-09-04 (**TODAY**)! @ 16:00 UTC - Fedora 27 Blocker Review Meeting

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

Hi folks! We currently have 7 proposed Beta blockers and 3 proposed
Final blockers to review, so let's have a Fedora 27 blocker review
meeting.

2017-09-04 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-09-04
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's time for another meeting! Let's check in on F27, and a couple of
new ideas...

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 27 status
3. Kernel rebase testing plan
4. Activity meeting plan
5. Open floor

Proposal to CANCEL: 2017-08-28 Fedora QA Meeting (and blocker review meeting)

Hi folks! I'm proposing we cancel the QA meeting tomorrow. I'll be
travelling to Flock, as I suspect a lot of other folks will be too.

For the same reason I think tomorrow would be a bad time for a blocker
review meeting, but we *do* need to run one, so I'll try and schedule
one for later in the week, with Flock folks attending in person, if
possible.

If anyone does want to go ahead and run either meeting, please do say
so. Thanks!

2017-08-21 @ 16:00 UTC - Fedora 27 Blocker Review Meeting

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

Hi folks! We currently have 8 proposed Beta blockers and 5 proposed
Final blockers to review, so let's have a Fedora 27 blocker review
meeting.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

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.

Proposal to CANCEL: 2017-08-21 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have
anything super important for the agenda. If you're aware of anything
important we have to discuss this week, please do reply to this mail
and we can go ahead and run the meeting. Thanks!

openQA test failures due to typing errors

Hi folks! Another note for anyone paying attention to openQA test
results.

Since 2017-08-09 there's been kind of a flood of failures caused by
'typing errors' - that is, when the test runner is trying to type a
string into the test VM and it doesn't get through correctly (usually
due to one or more keypresses being dropped).

Many 'map' SELinux denials in current Rawhide

Hi folks!

Just wanted to give a heads-up on this: it seems that a recent selinux-
policy update, 3.13.1-269 , introduced a new permission called 'map'.
This seems to have resulted in rather a large amount of new SELinux
denials for this permission in various cases. Some are fairly serious -
e.g.

2017-08-14 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-08-14
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's time for another meeting! Let's see where we stand for F27 and
so on.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 27 status
3. Test Day status
4. Onboarding status
5. Open floor

Proposal to CANCEL: 2017-08-07 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have
anything super important for the agenda, and tomorrow is a vacation day
at least in Canada and I think possibly in the US as well. If you're
aware of anything important we have to discuss this week, please do
reply to this mail and we can go ahead and run the meeting. Thanks!

'No More Alphas': wiki revision drafts

Hi, folks! So I've (finally) got ready an initial round of draft
changes to various wiki pages for the purpose of implementing the 'No
More Alphas' Change.

2017-07-31 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-07-31
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's time for another meeting! It's mostly going to be F27 planning
stuff this week.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. 'No more Alpha' status update
3. Fedora 27 Change review and test planning
4. Open floor

openQA failures caused by arch mismatch

Hi, folks! This is just a heads-up for anyone who's been watching the
openQA test results for an update, or something, and been confused.

A few days ago we added a new ppc64 openQA worker host box; ultimately
we're aiming to enable some of the openQA tests to run on ppc64 as well
as x86_64 and i686.

libglvnd-egl needed for X: should it be in base-x comps group? Or should something require it?

Hi folks! Wanted to run this up the flagpole somewhere before I just
went and did it...

We have a couple of openQA tests which just run Firefox on top of a
bare X server to do some browser tests.

Proposal to CANCEL: 2017-07-24 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow. We met the
last couple of weeks, and I think a lot of us are still catching up on
tasks from those meetings (at least I am). If you're aware of anything
important we have to discuss this week, please do reply to this mail
and we can go ahead and run the meeting.

openQA brief outage

Hey folks! Heads up: there is a brief openQA outage at present while I
upgrade the production instance to Fedora 26. Staging was already
upgraded last week, so there shouldn't be any big problems. Thanks!

Blocker bug process proposal: waiving late-discovered blockers to next release

Hi, folks!

So, during the blocker review process in the last few cycles, we have
several times come up against the unfortunate situation that a bug that
in the usual course of events would block a release is discovered
extremely late - say the day before the go/no-go meeting - and at least
some folks have argued that it's sometimes appropriate to not block the
release in this case.

This position has gained quite a bit of acceptance, and we agreed at
the F26 Final go/no-go meeting to draft up some formal policy for this
so we can make such decisions consistently and not in an ad hoc way
that

2017-07-17 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-07-17
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We didn't get through everything last week, so let's have a follow-up
meeting.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 27 planning
3. Storage test matrix update status
4. Open floor

2017-07-10 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-07-10
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

Fedora 26 is signed off, so let's check in on its status and any
remaining tasks, then take a first look at what's coming up in the
Fedora 27 cycle.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 26 status / retrospective
3. Fedora 27 planning
4. Test Day status
5. Open floor

Fedora 26 Candidate RC-1.5 Available Now!

** NOTE ** RC-1.5 is a kind of 'conditional' compose. The sole
difference to RC-1.4 (bar anything that went odd in the compose
process) is the qemu update for
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde">https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde</a> . So
aside from virt guest tests, most other results should be transferable
from RC-1.4. Still, at least smoke testing each image would be great.
We may wind up shipping RC-1.4, shipping RC-1.5, or not shipping
either; it'll be decided at the Go/No-Go meeting in the morning.

According to the schedule [1], Fedora 26 Candidate RC-1.5 is now
available for testing.

Another Fedora 26 test request: VMware

Hi folks! Got another request for Fedora 26 Final testing: can folks
please try booting RC-1.4 in VMware? For me, the Workstation live fails
to boot properly, in various configurations; in comparison the F25
Final Workstation live boots fine. That worried me a bit, so it'd be
good to hear results from other testers...

Fedora 26 status and testing requests: qemu , totem , and validation

Hi folks! Just wanted to send out a roll-up mail with some specific
requests for testing related to the Fedora 26 release.

1. There's a new qemu build which should fix the proposed blocker
#1467599 . It would be great if anyone who runs F26 and uses virt-
manager, Boxes or qemu in any other way could update to it and check
that it works OK:

<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde">https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde</a>

We don't just need testing from folks who were affected by the bug, but
by anyone who uses qemu, to ensure the change doesn't cause any other
problems.

2.

Fedora 26 Candidate RC-1.4 Available Now!

According to the schedule [1], Fedora 26 Candidate RC-1.4 is now
available for testing. Please help us complete all the validation
testing!

Proposal to CANCEL: 2017-07-03 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow. It's a
holiday in the U.S. and in Canada, and in any case we have little to
discuss right now as our efforts should mainly be focused on Fedora 26
Final testing. If you're aware of anything that urgently needs
discussing, please do reply to this mail and we can try to go ahead and
run the meeting, though it depends on people being around to run and
attend it.