# F32 Blocker Review meeting
# Date: 2020-03-30
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 4 proposed Final blockers and 4 proposed Final
freeze exception to review, so let's have a Fedora 32 blocker review
meeting tomorrow!
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/ .
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 F32 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
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
# Fedora Quality Assurance Meeting
# Date: 2020-03-30
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
Fedora 32 Final is winding up now, and we have a bunch of community
events coming up and stuff, so let's get together and check in.
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. F32 Final status and plans
3. Criteria / test case changes and proposals
4. Test Day / community event status
5. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
tl;dr: a scriptlet has been added to the fedora-release package that
performs a _one time_ "dnf module reset eclipse" operation when
fedora-release is upgraded. The update that does this is now in bodhi [1].
This was decided in a FESCo ticket [2] to solve bugzilla #1780827 [3]
and has a "F31 Common bugs" entry [4].
[1] https://bodhi.fedoraproject.org/updates/FEDORA-2020-af8b8d4da8
[2] https://pagure.io/fesco/issue/2356
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1780827
[4] https://fedoraproject.org/wiki/Common_F31_bugs#eclipse-module-reset
Longer explanation, quoting [4] in full:
> For a brief period, the eclipse module was a "default" module in
> Fedora 31 (meaning that a 'dnf install <package>' command would enable
> the module and install the modular version of <package> if <package>
> is part of the module). Such "shadowing" of non-modular packages is
> expected with modules, but the eclipse module was shadowing more
> packages than it should, so the module was made "non-default"
> again. Nevertheless, users who installed or upgraded affected packages
> in this window have the module persistently enabled and are not
> getting the non-modular versions of those rpms, even if those now have
> a higher version.
>
> To resolve this issue, a scriptlet was added to the fedora-release
> package that performs a one time 'dnf module reset eclipse'
> operation. This solves the issue of unexpected shadowing of packages,
> but at the same time creates a problem for users who have the eclipse
> module enabled on purpose. They need to once re-enable the module if
> desired.
>
> Summary: fedora-release performs a one-time disablement of eclipse
> module. Users who wish to have the module enabled should execute
> 'dnf module enable eclipse:latest' once more.
Zbyszek
(on behalf of FESCo)
# F32 Blocker Review meeting
# Date: 2020-03-23
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 7 proposed Final blockers and 1 proposed Final
freeze exception to review, so let's have a Fedora 32 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 F32 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 tomorrow. We met
last week and I don't think we have any urgent business this week.
There will be a blocker review meeting.
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
Hey All,
Fedora 32 Cloud Test Day is underway!
A test day is an event where anyone can help make sure that changes in
Fedora are working well in the upcoming release. Fedora community
members often participate, but the public is welcome also. You only
need to be able to download materials (including some large files),
and read and follow technical directions step by step, to contribute.
The wiki page[0] for the Cloud test day has a lot of good information
on what and how to test. After you’ve done some testing, you can log
your results in the test day app[1].
[0] https://fedoraproject.org/wiki/Test_Day:2020-03-20_Cloud_Testday
[1] http://testdays.fedorainfracloud.org/events/79
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
Fedora 32 Beta Released
----------------------------------
The Fedora Project is pleased to announce the immediate availability
of Fedora 32 Beta, the next step towards our planned Fedora 32 release
at the end of April.
Download the prerelease from our Get Fedora site:
* Get Fedora 32 Beta Workstation: https://getfedora.org/workstation/download/
* Get Fedora 32 Beta Server: https://getfedora.org/server/download/
Or, check out one of our popular variants, including KDE Plasma, Xfce,
and other desktop environments, as well as images for ARM devices like
the Raspberry Pi 2 and 3:
* Get Fedora 32 Beta Spins: https://spins.fedoraproject.org/prerelease
* Get Fedora 32 Beta Labs: https://labs.fedoraproject.org/prerelease
* Get Fedora 32 Beta ARM: https://arm.fedoraproject.org/prerelease
## Beta Release Highlights
* New in Fedora 32 Workstation Beta is EarlyOOM enabled by default.
* Fedora 32 Workstation Beta also enables the fs.trim timer by default.
* Fedora 32 Workstation Beta includes GNOME 3.3.6.
* And more ...
For more details about the release, read the full announcement at
* https://fedoramagazine.org/announcing-the-release-of-fedora-32-beta/
or look for the prerelease pages in the download sections at
* https://getfedora.org/
Since this is a Beta release, we expect that you may encounter bugs or
missing features. To report issues encountered during testing, contact
the Fedora QA team via the mailing list or in #fedora-qa on Freenode.
Regards,
Mohan Boddu
Fedora Release Engineering.
# F32 Blocker Review meeting
# Date: 2020-03-16
# Time: ** 16:00 ** UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 4 proposed Final blockers to review (and two Beta
AcceptedPreviousRelease blockers to check in on), so let's have a
Fedora 32 blocker review meeting tomorrow!
Remember that daylight savings time started last weekend, so the
meeting is now at 16:00 UTC, not 17:00 UTC.
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/ .
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 F32 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
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
# Fedora Quality Assurance Meeting
# Date: 2020-03-16
# Time: ** 15:00 ** UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We just signed off on Beta, and I figure everyone needs something to do
while we all self-isolate anyway, so what's more fun than a QA
meeting?! (Don't answer that, please...)
Daylight savings time started in many places last week, so the meeting
time in UTC hsa changed. If you put your clocks forward recently, the
meeting will be at the same *local* time as always for you. If you
didn't, the meeting will be one hour *earlier* in local time. You can
always check the current UTC time by running 'date -u'.
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. F32 Beta release tasks, Final plans
3. COVID-19 impact on Fedora 32 validation
4. Test Day / community event status
5. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net