DevHeads.net

Postings by Adam Williamson

2017-06-19 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-06-19
# 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!

Beta is signed off now, so let's check in on the libdb mess, where we
stand with Final, and what else is going 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 26 status / libdb issues
3. Test Day status
4. Open floor

Proposal to CANCEL: 2017-06-12 Fedora QA Meeting

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.

2017-06-05 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-06-05
# 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!

Sorry for the late notice, but we haven't met for a while, and it'd
probably be good to check in on the status of Beta and some other
upcoming events and ongoing activities.

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
3. Test Day status
4.

Testing request: libdb and F26 upgrades

Hi folks!

So as you may have read, F26 Beta was held up by a tricky bug which
causes upgrades to hang in some situations:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1397087" title="https://bugzilla.redhat.com/show_bug.cgi?id=1397087">https://bugzilla.redhat.com/show_bug.cgi?id=1397087</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1394862" title="https://bugzilla.redhat.com/show_bug.cgi?id=1394862">https://bugzilla.redhat.com/show_bug.cgi?id=1394862</a>

There are updates in F24, F25 and F26 at present which we hope should
resolve this bug without causing other problems, but the code in
question is quite sensitive so we want to be as sure as possible that
it's good to go.

It would be great if folks can help test.

Proposal to CANCEL: 2017-05-29 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. There are a
few things we could talk about, but none of them is really urgent, we
still have Beta testing to do, Monday's a vacation in the U.S., and I'm
also moving house that day so I won't be around!

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.

RPM database issues in the last day or two

Hi folks!

If you ran into problems like RPM or dnf or related apps reporting
database errors or unexpected crashes in the last few days, it is
almost certainly due to a broken libdb update that was sent to updates-
testing briefly. libdb-5.3.28-18 and libdb-5.3.28-19 are both subject
to the bug. If you got either of those builds while they were in
updates-testing for F24, F25 or F26, please do downgrade back to libdb-
5.3.28-17 .

Proposal to CANCEL: 2017-05-22 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. We should
mostly be focused on Beta validation now, and I don't see any major
other topics that need discussing right now. If you're aware of any,
please do reply to this mail and we can go ahead and run the meeting.

Remember, we do have the blocker review meeting at 1600 UTC!

2017-05-15 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-05-15
# 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 haven't met for a bit, and we're coming up on the Beta freeze,
so let's have a quick check-in!

Fedora 26 Beta blocker status mail #1

Hi folks! The Fedora 26 Beta freeze is fast approaching (it's 2017-05-
16), so it's time for a blocker status mail.

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

1. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1448923" title="https://bugzilla.redhat.com/show_bug.cgi?id=1448923">https://bugzilla.redhat.com/show_bug.cgi?id=1448923</a>
ACTION: Preferably, Firefox maintainer (mstransky) to fix build on ARM

2. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1443415" title="https://bugzilla.redhat.com/show_bug.cgi?id=1443415">https://bugzilla.redhat.com/show_bug.cgi?id=1443415</a>
ACTION: dnf team to investigate problem and come up with a fix

3. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1446432" title="https://bugzilla.redhat.com/show_bug.cgi?id=1446432">https://bugzilla.redhat.com/show_bug.cgi?id=1446432</a>
ACTION: QA to build a test image and verify fix

4.

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

Hi folks! I'm proposing we cancel the QA meeting tomorrow,
unless someone else wants to run it. I'm on my way back home from
Linuxfest Northwest and will be getting in pretty late, and I'm not
sure I'm going to make it up to run a meeting. If anyone would like to
volunteer to run the meeting, please just go ahead and send out an
agenda.

Remember, we do have the blocker review meeting at 1600 UTC!

Some dates for your diary: Beta freeze is 2017-05-16, and Beta Go/No-Go
is scheduled for 2017-05-25.

Proposal to CANCEL: 2017-05-01 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
have anything significant to discuss.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

openQA test results for critpath updates now shown in Bodhi

Hi folks! I thought this was worth sending out an announcement about so
as many packagers and testers as possible are aware of it.

With the rollout of Bodhi 2.6.0 to production today, openQA test
results for critpath updates now appear in the Bodhi webUI! Click the
'Automated Tests' tab on any critical path update (from the last two
months or so) and you should see, as well as the 'dist.*' tests you're
probably familiar with that are run by Taskotron, results for several
'update.*' tests.

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

# Fedora Quality Assurance Meeting
# Date: 2017-04-24
# 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!

I don't have a big agenda this week, but figured we might as well get
together for a quick check-in. We might go less than an hour if there
isn't a lot to talk about.

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
3. Test Day status
4. Action ideas?
5. Open floor

Proposal to CANCEL: 2017-04-17 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. It's a
holiday in many parts of the world, and we don't have anything specific
to discuss, I don't think.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

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

# Fedora Quality Assurance Meeting
# Date: 2017-04-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!

We have some active criteria / validation test proposals to discuss,
so that's a reason to have a meeting. And there appears to be stuff
ongoing in Atomic-land, I thought maybe roshi might know about that
and could update us.

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.

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

# Fedora Quality Assurance Meeting
# Date: 2017-04-03
# 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 haven't met for a couple of weeks, so let's get together and see
what's happening.

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
3. Test Day status
4. Open floor

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

Hi folks! I'm proposing we cancel the QA meeting tomorrow. Once again I
don't have anything significant for the agenda as we're mostly busy
with Alpha validation. We'll likely have stuff to check in on next week.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

Fedora 26 Alpha status update

Hi folks! Just wanted to let everyone know where we're at with the F26
Alpha.

An Alpha RC2 compose request is in, and RC2 should be building at
present. The main change between RC1 and RC2 is a fix for the problems
with gnome-initial-setup: it should now work properly if you don't
create a user during install. There's also an updated selinux-policy
which should hopefully squish all the AVCs we've been seeing during
regular install and boot. It should arrive some time this evening US
time, all being well.

There does still seem to be some kind of kernel issue.

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

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have
anything significant for the agenda, I think we covered everything
pretty well last week.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

2017-03-13 @ **15:00** UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-03-13
# 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 haven't met for a couple of weeks, we're getting close to F26 Alpha,
and there are a few other issues we could perhaps talk about, so let's
have a meeting!

Unannounced soname bump (Rawhide and 26): ldns (libldns.so.1 -> libldns.so.2)

ldns was updated from 1.6.17 to 1.7.0 for Rawhide and Fedora 26 on
2017-03-06. This update bumped the soname from libldns.so.1 to
libldns.so.2 .

2017-03-06 @ 17:00 UTC - Fedora 26 Blocker Review

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

Hi folks!

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

Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have
anything significant for the agenda, I think we covered everything
pretty well last week.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

Sorry for the late notice, forgot to send this yesterday and I've been
out all day today...

New automated test coverage: openQA tests of critical path updates

Hi folks!

I am currently rolling out some changes to the Fedora openQA deployment
which enable a new testing workflow. From now on, a subset of openQA
tests should be run automatically on every critpath update, both on
initial submission and on any edit of the update.

For the next little while, at least, this won't be incredibly visible.
openQA sends out fedmsgs for all tests, so you can sign up for FMN
notifications to learn about these results. They'll also be
discoverable from the openQA web UI - <a href="https://openqa.fedoraproject.org" title="https://openqa.fedoraproject.org">https://openqa.fedoraproject.org</a>
.

2017-02-27 @ 17:00 UTC - Fedora 26 Blocker Review

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

Hi folks! We currently have 2 proposed Alpha blockers, and 2 proposed
Final blockers to review, so let's have a Fedora 26 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: 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.

2017-02-27 @ 16:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-02-27
# Time: 16: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!

I don't have a huge amount of specific topics for a meeting, but it's
been a couple of weeks and we are getting closer to Fedora 26 Alpha:
the Fedora 26 branching is scheduled to happen on Tuesday. There are
also some interesting proposed Changes for Fedora 27 we could look at.

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

Proposal to CANCEL: 2017-02-20 Fedora blocker review meeting

Hi folks! I'm proposing we cancel tomorrow's blocker review meeting.
There's just one proposed Alpha blocker to review:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1405790" title="https://bugzilla.redhat.com/show_bug.cgi?id=1405790">https://bugzilla.redhat.com/show_bug.cgi?id=1405790</a>

and no proposed Alpha freeze exceptions. The proposed blocker should be
pretty straightforward, so if a few people can vote in the bug, we
should be good.

Thanks folks!

Proposal to CANCEL: 2017-02-20 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have
anything significant for the agenda, I think we covered everything
pretty well last week.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

Intent to orphan: trac-defaultcc-plugin , trac-condfieldsgenshi-plugin

I was maintaining these packages for use with fedorahosted trac
instances. Since fedorahosted is being retired, I'm really not
interested in them any more, so I'm planning to orphan them soon.
Anyone who wants them is welcome to them.

New list for ResultsDB users

Hi folks! So I've been floating an idea around recently to people who
are currently using ResultsDB in some sense - either sending reports to
it, or consuming reports from it - or plan to do so. The idea was to
have a group where we can discuss (and hopefully co-ordinate) use of
ResultsDB - a place to talk about result metadata conventions and so
forth.

It seemed to get a bit of traction, so I've created a new mailing list:
resultsdb-users .