Fedora Linux 36 Beta Released
------------------------------------------
The Fedora Project is pleased to announce the immediate availability
of Fedora 36 Beta, the next step towards our planned Fedora 36 release
at the end of April.
Download the prerelease from our Get Fedora site:
* Get Fedora 36 Beta Workstation:
https://getfedora.org/workstation/download/
* Get Fedora 36 Beta Server: https://getfedora.org/server/download/
* Get Fedora 36 IoT: https://getfedora.org/iot/download/
Or, check out one of our popular variants, including KDE Plasma, Xfce,
and other desktop environments, as well as images for ARM devices:
* Get Fedora 36 Beta Spins: https://spins.fedoraproject.org/prerelease
* Get Fedora 36 Beta Labs: https://labs.fedoraproject.org/prerelease
* Get Fedora 36 Beta ARM: https://arm.fedoraproject.org/prerelease
## Beta Release Highlights
* Fedora 36 Workstation Beta includes GNOME 42
* Update of programming languages and libraries: LXQt 1.0, Golang 1.18,
Ruby 3.1
For more details about the release, read the full announcement at
* https://fedoramagazine.org/announcing-fedora-36-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 test(a)lists.fedoraproject.org mailing list or
in #fedora-qa on Libera Chat or the #qa:fedoraproject.org Matrix room.
Regards,
Tomas Hrcka
Fedora Release Engineering.
# F36 Blocker Review meeting
# Date: 2022-03-28
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 6 proposed Final blockers and 2 proposed Final freeze
exception issues to review, so let's have a review meeting on Monday.
Remember, Europeans, if DST kicks in for you this weekend, the meeting
time will change for you this week, back to the time it usually is
except for this one weird intermission every year. :D
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 F36 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
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
# Fedora Quality Assurance Meeting
# Date: 2022-03-28
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat
Greetings testers!
It's been a couple of weeks since we met, and Beta has been signed off,
so let's get together and take a look at Final plans and see where we
are with events and stuff.
Remember, Europeans, if DST kicks in for you this weekend, the meeting
time will change for you this week, back to the time it usually is
except for this one weird intermission every year. :D
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 36 Beta wrap-up and Final planning
3. Current criteria / test case proposals
4. Test Day / community event status
5. Open floor
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
I have returned from PTO, so you're getting this reminder ~2 hours
prior to the meeting instead of the usual "the day before." But in any
case, the Fedora Linux 36 Beta Go/No-Go[1] meeting
is scheduled for Thursday 24 March at 1700 UTC in #fedora-meeting. At
this time, we will determine the status of the F36 Beta for the 29
March target date #2[2]. For more information about the Go/No-Go
meeting, see the wiki[3].
[1] https://calendar.fedoraproject.org/meeting/10209/
[2] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
[3] https://fedoraproject.org/wiki/Go_No_Go_Meeting
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
# F36 Blocker Review meeting
# Date: 2022-03-21
# Time: ** 16:00 ** UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 1 proposed Beta blocker, 1 proposed Beta freeze
exception issue, and 4 proposed Final blockers to review, so let's
have a review meeting on Monday.
Remember DST started in North America last week, and check the meeting
time carefully! If you're in North America it's at the same time as
always, if you're anywhere else it's likely earlier (when DST starts in
Europe it'll be back to the 'usual' time there).
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 F36 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
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net