2015-01-26 @16:00 UTC - Fedora QA Meeting
by Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2015-01-26
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We haven't met for a bit, so let's get together and check in on where
we're all at. I'm expecting roshi will announce a blocker bug review
meeting to follow the QA meeting, as we agreed. Please, if you have
any further items to add to the agenda, reply to this mail and we can
add them! Thanks folks.
== Proposed Agenda Topics ==
1. Fedora 22 testing status
2. Fedora 22 Change check-in
3. Release criteria status
4. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
8 years, 8 months
Urgent F21 testing request: libhif and PackageKit
by Adam Williamson
Hi, folks!
We recently found out that there were some significant problems with
PackageKit and things that use it (GNOME Software, Apper, gnome-
packagekit...) in Fedora 21, since the release of libhif-0.1.7 as an
update shortly after F21 came out. The initial bug people noticed was
offline updates failing to work, but in subsequent testing we found
that regular package install and remove operations could cause crashes
in PackageKit-based apps and it was possible for the PackageKit
database to be corrupted.
It would be great if folks could, as a matter of urgency, test this
update:
https://admin.fedoraproject.org/updates/PackageKit-1.0.4-1.fc21,libhif-
0.1.8-1.fc21
Please install the updated packages, reboot (or at least restart the
packagekit service), run 'pkcon repair' as root, reboot again, and
then test regular use of GNOME Software and pkcon as much as possible -
try installing and removing packages, running offline updates, and so
on. If your package set is up to date you can try downgrading a
package in order to test offline updates - try 'yum downgrade
devassistant', for instance, if you have it installed, then check for
updates in GNOME Software.
As the bugs were pretty serious we'd like to release the fix as soon
as possible, but at the same time we want to make sure we tested it
thoroughly.
Thanks folks! And thanks a lot to Richard Hughes for working to fix
this quickly, and Kamil for doing a lot of testing on it.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
8 years, 8 months
Proposal to CANCEL: 2015-01-19 Fedora QA Meeting
by Adam Williamson
Hi folks! Once again there's nothing much on the agenda this week. We
also don't have any proposed blockers to review, so no need to do
that. Probably we can get back into the swing next week as we start to
approach the Fedora 22 branch point (yep, it's coming!), but for now I
think we can take the morning off again.
A new build of anaconda with some major changes landed yesterday, but
neither yesterday's nor today's nightly Rawhide boot.iso composes
succeeded, so we don't have images to test at present. As usual the
bot will nominate the next nightly where we get a boot.iso and we'll
be able to test all the new bits.
Thanks folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
8 years, 8 months
Proposal to CANCEL: 2015-01-12 Fedora QA Meeting
by Adam Williamson
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
8 years, 8 months
2015-01-07 @ 1600 UTC ** Fedora 22 Blocker Review Meeting
by 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
8 years, 8 months