2024-05-27 - Fedora Quality Meeting - Minutes
by Adam Williamson
=====================================
# #meeting:fedoraproject.org: Quality
=====================================
Meeting started by @meetbot:fedora.im at 2024-05-27 07:54:05
Meeting summary
---------------
* TOPIC: Roll Call (@adamwill:fedora.im, 15:00:18)
* TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:04:59)
* INFO: no action items for follow-up (@adamwill:fedora.im, 15:05:12)
* INFO: welcome the new, chattier meetbot (@adamwill:fedora.im,
15:05:38)
* TOPIC: Fedora 41 status (@adamwill:fedora.im, 15:09:44)
* INFO: f41 seems to be ticking over fine ATM, no major issues
(@adamwill:fedora.im, 15:09:55)
* INFO: the anaconda team is now targeting the web UI shift for
F42, not F41. We discussed whether we have a preference about exactly
when and where to flip it (off in Rawhide now and on again after F41
branches, or off in F41 right after it branches) and decided to leave it
up to the devs (@adamwill:fedora.im, 15:18:16)
* TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:20:05)
* INFO: kernel 6.9 test week is ongoing at
https://fedoraproject.org/wiki/Test_Day:2024-05-26_Kernel_6.9_Test_Week
but performance result submission is broken, see
https://pagure.io/kernel-tests/issue/50 for details
(@adamwill:fedora.im, 15:21:27)
* INFO: we also had a podman 5.1 test day last week, thanks to all
who tested - https://testdays.fedoraproject.org/events/188
(@adamwill:fedora.im, 15:27:59)
* TOPIC: Open floor (@adamwill:fedora.im, 15:29:57)
Meeting ended at 2024-05-27 15:34:40
Action items
------------
People Present (lines said)
---------------------------
* @adamwill:fedora.im (40)
* @bittin:fedora.im (11)
* @frantisekz:fedora.im (6)
* @zodbot:fedora.im (4)
* @lruzicka:matrix.org (3)
* @meetbot:fedora.im (3)
* @jeffiscow:fedora.im (2)
* @derekenz:fedora.im (2)
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
2 weeks, 5 days
[Proposal] TestDays Category TestCase Tags
by Sumantro Mukherjee
Hello Testers,
Fedora QA has been hosting loads of test days for sometime (ie 15 test
days/release) which is why we author test cases. These test cases are
sometimes for features which may never see the light of day (at least
not in that particular release).
Sometimes, these test cases are integration test cases and are very
hard to categorize in package-specific test cases. Many times, due to
their non-blocking nature, they are not associated with "Release
Criterion". This makes test cases authored for a particular test day,
extremely hard to find and check for bitrot.
I propose the following:
a) Add a new category Category:CoreOS Test Cases
b) Add new Category TestDay:NAME
c) We already track the release cycle, Category:Fedora 41 Test Days
Benefits:
a) In the long run add more filtering functions to testday-stats on
test cases added
b) Easier navigation of test cases, written just for a test day and
updation of the same
c) Establishing scope for blocking criteria for upcoming features that
get tested in Rawhide Test Days
I would like to know your concerns and comments. If people are okay, I
can go do the homework :)
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
2 weeks, 5 days
[RFC] Rawhide Test Days
by Sumantro Mukherjee
Hey Folks,
Since some time, we have been asking more and more developers to test
features as they get to Rawhide or Copr. This gives the community and
QA by large, more room to test and find out bugs.
Timely done, this effort not only increases the quality of Fedora
releases but also gives more time to developers to fix these issues
before they become blockers. One part of this process is implementing
Rawhide Test Days.
Rawhide Test Days aims to use Rawhide as the base to test the upcoming
features/changes. The Test Days still follow the vanilla test day
SOP[0]. The context of the Rawhide Test Days has been drafted here
[1].
This is a good time, for us to register feedback and if you are a
team/team member; get involved, feel free to comment in the pagure
ticket[2] or this email!
Thanks a lot for the continued support and special thanks to DNF5 and
the Podman team who participated as pilots and tested their recent
features and changes!
[0] https://fedoraproject.org/wiki/QA/SOP_Test_Day_management
[1] https://fedoraproject.org/wiki/User:Sumantrom/Draft/QA:SOP_Rawhide_TestDay
[2] https://pagure.io/fedora-qa/issue/777
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
2 weeks, 6 days
2024-05-13 - Fedora Quality Meeting - Minutes
by Adam Williamson
=====================================
# #meeting:fedoraproject.org: Quality
=====================================
Meeting started by @adamwill:fedora.im at 2024-05-13 15:00:53
Meeting summary
---------------
* TOPIC: Roll Call (@adamwill:fedora.im, 15:00:58)
* TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:05:02)
* INFO: no action items from previous meeting (@adamwill:fedora.im,
15:05:29)
* TOPIC: Fedora 41 status (@adamwill:fedora.im, 15:07:48)
* INFO: Rawhide is currently pretty good, except a recently-pushed
package has broken some openQA tests, I'll look into that after the
meeting and try to prevent it reaching the compose
(@adamwill:fedora.im, 15:08:45)
* INFO: dnf5 by default has landed in rawhide, please test and
report any issues you find (@adamwill:fedora.im, 15:08:59)
* INFO: note some dnf5 commands have changed, it is not a 100%
drop-in replacement, so if a command doesn't work exactly as it did
before, check docs before filing an issue (@adamwill:fedora.im,
15:09:31)
* TOPIC: Test Day / community event status (@adamwill:fedora.im,
15:15:15)
* INFO: the call for test events for F41 was sent out recently
(@adamwill:fedora.im, 15:15:28)
* INFO: kernel 6.9 test week is planned for May 26 - Jun 1:
https://pagure.io/fedora-qa/issue/775 (@adamwill:fedora.im, 15:16:08)
* TOPIC: Open floor (@adamwill:fedora.im, 15:20:31)
Meeting ended at 2024-05-13 15:23:52
Action items
------------
People Present (lines said)
---------------------------
* @adamwill:fedora.im (33)
* @zodbot:fedora.im (5)
* @lruzicka:matrix.org (4)
* @nielsenb:fedora.im (3)
* @geraldosimiao:matrix.org (3)
* @jeffiscow:fedora.im (3)
* @blackwell:fedora.im (3)
* @meetbot:fedora.im (2)
* @derekenz:fedora.im (2)
* @tflink:fedora.im (1)
* @kparal:matrix.org (1)
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
1 month
[Testdays] Call for Fedora Linux 41 testing events
by Sumantro Mukherjee
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 41.
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/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
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 time frame 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 time frame 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:
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a 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 the 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!
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
1 month