==============================================
#fedora-meeting-2: Workstation WG (2024-11-05)
==============================================
Meeting started by brainycmurf at 04:28:49 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2024-11-08/workstation.2…
.
Meeting summary
---------------
* Present members: Michael, Allan, Neal, Matthias, Jens, Kalev, Chris
(brainycmurf, 04:28:49)
* Regrets: Tomas (brainycmurf, 04:28:50)
* Missing: Owen (brainycmurf, 04:28:52)
* Secretary: Chris (brainycmurf, 04:28:54)
* Fedora 41 release party presentation (brainycmurf, 04:28:56)
* LINK: https://pagure.io/fedora-workstation/issue/452 (brainycmurf,
04:28:58)
* This is on track (brainycmurf, 04:29:00)
* Release Party presentations deadline is tomorrow! (brainycmurf,
04:29:02)
* LINK: https://pagure.io/fedora-workstation/issue/452#comment-942142
(brainycmurf, 04:29:04)
* Please support org.freedesktop.locale1 keyboard configuration for
Anaconda on Live environment (brainycmurf, 04:29:06)
* LINK: https://pagure.io/fedora-workstation/issue/430 (brainycmurf,
04:29:09)
* Anaconda arch may be changing in F42 (brainycmurf, 04:29:13)
* there are tags in gitlab, no centralized process or gitlab project;
each app project is responsible for accessibility (brainycmurf,
04:29:55)
* Announcements (brainycmurf, 04:29:58)
* Fedora 41 has been released! (brainycmurf, 04:30:00)
* Positive reviews (brainycmurf, 04:30:02)
* Minutes from last week (brainycmurf, 04:30:04)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2024-10-23/workstation.2…
(brainycmurf, 04:30:06)
Meeting ended at 04:30:09 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (41)
* zodbot (7)
* Neal (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 42.
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 <https://redhat.com/trusted>
==============================================
#fedora-meeting-2: Workstation WG (2024-10-22)
==============================================
Meeting started by brainycmurf at 01:52:28 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2024-10-23/workstation.2…
.
Meeting summary
---------------
* Present members: Michael, Allan, Neal, Matthias, Jens, Kalev, Owen,
Chris (brainycmurf, 01:52:29)
* Regrets: Tomas (brainycmurf, 01:52:29)
* Missing: (brainycmurf, 01:52:31)
* Secretary: Kalev (brainycmurf, 01:52:33)
* Fedora 41 release readyness (brainycmurf, 01:52:35)
* LINK: https://pagure.io/fedora-magazine-newsroom/issue/323
(brainycmurf, 01:52:38)
* Magazine article is coming. Christian Schaller has been collecting
some internal notes. (brainycmurf, 01:52:40)
* ACTION: Neal to file a Workstation ticket to track the release party
presentation (brainycmurf, 01:52:52)
* Barriers to entry for helping with Workstation developement
(brainycmurf, 01:52:59)
* Announcements and status reports (brainycmurf, 01:53:08)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2293628
(brainycmurf, 01:53:20)
* Minutes from last week (brainycmurf, 01:53:22)
* LINK:
https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.o…
(brainycmurf, 01:53:26)
Meeting ended at 01:53:29 UTC.
Action Items
------------
* Neal to file a Workstation ticket to track the release party
presentation
Action Items, by person
-----------------------
* Neal
* Neal to file a Workstation ticket to track the release party
presentation
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (29)
* zodbot (7)
* Neal (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
# F10 Blocker Review meeting
# Date: 2024-10-21
# Time: 16:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 41 blocker review meeting! We have 6
proposed blockers and 2 proposed freeze exceptions for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
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/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
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 F40 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
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
# F10 Blocker Review meeting
# Date: 2024-10-14
# Time: 16:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 41 blocker review meeting! We have 3
proposed blockers and 6 proposed freeze exceptions for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
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/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
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 F40 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
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net