I created a first draft of a questionnaire of Server users on hacked.io as decided in our meeting:
https://hackmd.io/0B4Tpe8hTQ2N9IN91VKkAw
Please, add your ideas and/or comment on the proposal.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
After a short discussion with Adam about Server QA testing, I started a new Server Wiki page to list manually QA tests. Some of them may get scripted in automatic QA testing.
See https://fedoraproject.org/wiki/Server/QA_Manual_Testing_Overview for a first initial draft of some examples.
What do you think about it?
Peter
—
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
# F10 Blocker Review meeting
# Date: 2024-09-09
# 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 1
proposed blocker and 10 proposed freeze exceptions for Beta.
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!**
Especially since we have so many proposed FEs right now, it would
really help make the meeting shorter if people can vote on them today.
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
The upcoming meeting will be held on
==========================================================================
Fedora Server MATRIX meeting Wednesday, Sep 04 17:00 ==UTC==
https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha…
==========================================================================
Please, check your local time using date -d '2024-09-04 17:00UTC'
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
=== 1. Follow up actions and announcements ===
=== 2. Ansible assisted installation and configuration of NFS service ===
!link https://pagure.io/fedora-server/issue/138
Continuing our discussion at last week's meeting after trying out and testing the current scripts.
30 mins max
=== 3. Testing Release 41
!link https://pagure.io/fedora-server/issue/144
Determine which tests we want to carry out and who will perform which tests.
20 mins _min_
=== 4. Open Floor
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
https://pagure.io/fedora-server/boards/Works%20in%20progress
===== Pending Topics for Follow-Up Meetings =====
=== Using Ansible to install and configure Wildfly
!link https://pagure.io/fedora-server/issue/60
=== Fedora Server in a virtualized runtime environment ===
link https://pagure.io/fedora-server/issue/110
=== Revisiting Fedora Server quality criteria and procedures
link https://pagure.io/fedora-server/issue/63
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
# F10 Blocker Review meeting
# Date: 2024-09-03 (**TUESDAY**)
# 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! As Monday
is a holiday in North America, let's do it on Tuesday instead. We have
7 proposed freeze exceptions for Beta.
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 this weekend, 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 holiday weekend and see you on Tuesday!
[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
I am a newbie at markdown syntax and this is my first attempt to
publish anything using markdown in pagure.
I have tried to describe what is necessary to run the nfs_service
ansible role. I did my best to describe what needs to be done from the
standpoint of someone new to both nfs and ansible.
The writeup is located in the "stg" branch of pagure.io. The file is
https://www.pagure.io/fedora-server/blob/stg/f/fedora-ansible/roles/nfs_ser…
Feedback is most certainly welcome.
Running each of the other three nfs ansible roles found in the "stg"
branch follows the same general template.
The upcoming meeting will be held on
==========================================================================
Fedora Server MATRIX meeting Wednesday, Aug 28 17:00 ==UTC==
https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha…
==========================================================================
Please, check your local time using date -d '2024-08-28 17:00UTC'
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
=== 1. Follow up actions and announcements ===
=== 2. Ansible assisted installation and configuration of NFS service ===
!link https://pagure.io/fedora-server/issue/138
Continuing our discussion at last week's meeting about how we want to distribute the service specific Ansible playbooks.
30 mins max
=== 3. Optimizing NFS service documentation ===
!link https://pagure.io/fedora-server/issue/138
!link https://docs.stg.fedoraproject.org/en-US/fedora-server/services/filesharing…
30 mins max
=== 4. Testing Release 41
No tracking issue yet
10 mins _min_
=== 5. Open Floor
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
https://pagure.io/fedora-server/boards/Works%20in%20progress
===== Pending Topics for Follow-Up Meetings =====
=== Using Ansible to install and configure Wildfly
!link https://pagure.io/fedora-server/issue/60
=== Fedora Server in a virtualized runtime environment ===
link https://pagure.io/fedora-server/issue/110
=== Revisiting Fedora Server quality criteria and procedures
link https://pagure.io/fedora-server/issue/63
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast