[Test Days] Fedora Media Writer 2019-04-30
by Sumantro Mukherjee
Hey Testers,
Tuesday 2019-04-30 will be Fedora Media Writer Test Day[0]!
This Test Day will focus on Fedora Media Writer. Fedora Media Writer is
used for creating bootable flash drives on different operating systems and
architectures.
The tool is intended to be provided as the primary download option since
Fedora 25, with the aim of lowering the barrier for potential users to try
and install Fedora.
In this test day, we aim to test both Fedora 29 ,Fedora 30 and Fedora
Rawhide pre-release boot-media creation on Windows, OS X, and Fedora,
specifically targeting the creation of ARM-bootable media to see whether
it's working well enough and catch any remaining issues.
It's also pretty easy to join in: all you'll need is 4GB flash drive (With
all it's *data backed up*).
As always, the event will be in #fedora-test-day on Freenode IRC.
[0]: https://fedoraproject.org/wiki/Test_Day:2019-04-30_Fedora_Media_Writer
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
4 years, 5 months
Call For Test Days for Fedora 31!
by Sumantro Mukherjee
Hi Fedora users, developers and friends!
It's time to start thinking about Test Days for Fedora 31.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/583 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at <goog_29817696>
https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development schedule
<https://fedoraproject.org/wiki/Releases/31/Schedule>, though, in deciding
when
you want to run your Test Day - for some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific timeframe due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or timeframe you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to help
with another, feel free to join one or more of already accepted Test Days:
2019-04-30 Fedora Media Writer Test Day
GNOME Test Day
Silverblue Test Day*
i18n Test Day*
Kernel Test Week*
Upgrade Test Day*
And don't be afraid, there are lot of more slots available for your own
Test Day!
[*] These are the test days we run generally to make sure everything is
working fine, the dates get announced as we move into release cycle.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!
Best Regards,
Sumantro
Fedora QE
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
4 years, 5 months
2019-04-29 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2019-04-29
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We didn't meet for nearly a month, what with Fedora 30 Final and
holidays and things, so let's get together, wave goodbye to Fedora 30
and plan ahead.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
Of course there will be no blocker review meeting, as 30 is signed
off now. We'll break for at least a little bit before starting on
F31 blocker review!
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 30 wrap-up / final tasks
3. Xen release criterion
4. Late-discovered blocker waive proposal
5. Test Day / community event status
6. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 5 months
Fedora 30 Final RC status
by Adam Williamson
Hey folks!
Just to keep everyone in the loop, here's what's going on:
RC1 was pretty close to shipping at the Go / No-Go, but there were a
couple of bugs we wanted to fix and we didn't feel like it had been
baked long enough to sign off today.
So, an RC2 is building with four targeted fixes:
* [pim-sieve-editor-18.12.2-2.fc30](
https://bodhi.fedoraproject.org/updates/FEDORA-2019-e5343ff7b6) for
[#1670396](https://bugzilla.redhat.com/show_bug.cgi?id=1670396)
* [anaconda-30.25.6-2.fc30](
https://bodhi.fedoraproject.org/updates/FEDORA-2019-7184d9d0c0) for
[#1703152](https://bugzilla.redhat.com/show_bug.cgi?id=1703152)
* [buildah-1.7-18.git873f001.fc30](
https://bodhi.fedoraproject.org/updates/FEDORA-2019-a329c204c3) for
[#1702419](https://bugzilla.redhat.com/show_bug.cgi?id=1702419)
* [swid-tools-0.8.1-1.fc30](
https://bodhi.fedoraproject.org/updates/FEDORA-2019-1d9e7f3b5b) for
[#1703066](https://bugzilla.redhat.com/show_bug.cgi?id=1703066)
aside from those, RC2 will be identical to RC1. RC2 should be complete
in something like 4-6 hours from now; an email will be sent when that
happens. Testing RC1 is still valuable at this point, as the changes in
RC2 are quite minor.
So, please continue to test RC1 for now, and switch over to testing RC2
when it lands. As well as running tests from the matrices, if folks can
just do exploratory testing and try to run the images on as many
configurations as possible and look for any major issues, that'd be
great.
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 5 months
