Hey All,
A new change proposal has been submitted for the Fedora 33 release
cycle which entails the usage of Btrfs by default [0] for Workstations and
Spins across x86_64 and ARM architectures, As a result, we have
organized a test week from Monday, Aug 31, 2020. As a part of this test
week, we will aim at folks running a VM or bare metal install with
Btrfs as storage and sharing their experience for the following scenarios:
1. Install use it normally for a week and report any and all issues,
concerns, questions that come up
2. Testing the BlivetGUI installer options along with the Custom
3. Suspend to RAM
4. Suspend to Disk
5. Reinstalling F33 on an installed Fedora partition and preserving
/home and its data
6. Help find outdated docs and report them to QA team and WS team
Results can be submitted for the test cases[2]
Refer to the wiki page[1] for links to the test cases and materials
you’ll need to participate!
As usual, we will hang out on the #fedora-test-day over Freenode to
address questions
[0] https://fedoraproject.org/wiki/Changes/BtrfsByDefault
[1] https://fedoraproject.org/wiki/Test_Day:2020-08-31_Btrfs_default
[2]https://testdays.fedorainfracloud.org/events/92
Thanks
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
# F33 Blocker Review meeting
# Date: 2020-08-31
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 3 proposed Beta blockers, 1 proposed Final blocker
and 4 proposed Beta freeze exceptions to review, so let's have a Fedora
33 blocker review meeting on Monday!
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/ .
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 F33 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 weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Hi folks! I'm proposing we cancel the QA meeting for Monday. I don't
have anything urgent this week. We can discuss the network criterion in
the blocker review meeting, I think.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Hi all,
Today's an important day on the Fedora 33 schedule[1], with several
significant cut-offs. First of all, today is the Bodhi activation point
[2]. That means that from now on all Fedora 33 packages must be
submitted to updates-testing and pass the relevant requirements[3]
before they will be marked as 'stable' and moved to the fedora
repository.
Today is also the Beta freeze[4]. This means that only packages which
fix accepted blocker or freeze exception bugs[5][6] will be marked as
'stable' and included in the Beta composes. Other builds will remain
in updates-testing until the Beta release is approved, at which point
the Beta freeze is lifted and packages can move to 'stable' as usual
until the Final freeze.
Today is also the '100% code complete deadline' Change
Checkpoint[5], meaning that Fedora 33 Changes must now be code
complete, meaning all the code required to enable the new change is
finished. The level of code completeness is reflected as tracker bug
state ON_QA. The change does not have to be fully tested by this
deadline'.
Finally, today is also the Software String freeze[7], which means that
strings marked for translation in Fedora-translated projects should
not now be changed for Fedora 33.
Tomas Hrcka
jednorozec on FreeNode #fedora-releng #fedora-devel #fedora-cs
[1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
# Fedora Quality Assurance Meeting
# Date: 2020-08-24
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
Fedora 33 has branched, and we have a couple of criteria proposals to
discuss, so let's have a meeting on Monday!
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 33 status
3. Criteria proposals: log in/out, networking...
4. Test Day / community event status
5. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
# F33 Blocker Review meeting
# Date: 2020-08-24
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have only 1 proposed Beta blocker to review at present,
but more may well show up over the weekend, so let's have a Fedora 33
blocker review meeting on Monday!
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/ .
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 F33 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 weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Hey All
Fedora 33 GNOME 3.37 Test Day is happening[0] now.
This is the time when we test the new features and version bumps of
all the GNOME apps which came with the megaupdate.
You can use the latest F33 image (pointed on the wiki) for this Test Day.
If you have some spare time, please help run the test cases
mentioned[1] and report the bugs on Gnome GitLab or RHBZ (if it's
Fedora specific).
[0] https://fedoraproject.org/wiki/Test_Day:2020-08-19_Fedora_33_Gnome_3.37
[1] https://testdays.fedorainfracloud.org/events/91
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED