Fedora 33 Beta Released
----------------------------------
The Fedora Project is pleased to announce the immediate availability
of Fedora 33 Beta, the next step towards our planned Fedora 33 release
at the end of October.
Download the prerelease from our Get Fedora site:
* Get Fedora 33 Beta Workstation: https://getfedora.org/workstation/download/
* Get Fedora 33 Beta Server: https://getfedora.org/server/download/
* Get Fedora 33 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 33 Beta Spins: https://spins.fedoraproject.org/prerelease
* Get Fedora 33 Beta Labs: https://labs.fedoraproject.org/prerelease
* Get Fedora 33 Beta ARM: https://arm.fedoraproject.org/prerelease
## Beta Release Highlights
* All of the desktop variants of Fedora 33 Beta will use BTRFS as the
default filesystem.
* Fedora 33 Workstation Beta includes GNOME 3.38
* With Fedora 33 Beta, Fedora IoT is now an official Fedora Edition.
* And more ...
For more details about the release, read the full announcement at
* https://fedoramagazine.org/announcing-the-release-of-fedora-33-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 Freenode.
Regards,
Mohan Boddu
Fedora Release Engineering.
Hey,
Fedora 33 IoT test day is on 2020-09-30. As Fedora IoT becomes the
part of Fedora Editions, to ensure we test the bits properly, we are
going to have a test day [0] where we will be focusing on testing the
IoT builds and reporting bugs.
[0] ttp://fedoraproject.org/wiki/Test_Day:2020-09-30_Fedora_33_IoT_Edition
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
Hi folks! I'm proposing we cancel the QA meeting for Monday. I'm off
sick at the moment, and have some medical appointments that morning.
It's also a public holiday in Czech, so all the RH folks from that
office won't be around to run or attend the meeting. If there is a
desire to have the meeting, someone else can volunteer to run it :)
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
# F33 Blocker Review meeting
# Date: 2020-09-28
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 3 proposed Final blockers and 1 proposed Final
freeze exception,
so we'll 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/ .
** NEW ** - you can also now vote on bugs outside of review meetings!
For the Fedora 33 cycle we enabled a new voting system and have been
using it pretty heavily. 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.
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
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
Hi everyone,
No cancelations this time! The Fedora 33 Beta Go/No-Go[1] meeting is
scheduled for Thursday 24 September. We will meet at 1700 UTC in
#fedora-meeting-1 to determine if we will release Fedora 33 Beta.
[1] https://apps.fedoraproject.org/calendar/meeting/9810/
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
Hey All,
As we come closer to Fedora 33 Beta, it's time to test upgrades.
Fedora 33 has a lot of changesets [0] and it becomes essential that we
test the graphical upgrade
methods as well as the command line.
As a part of this test day[1], we will test upgrading from a full
updated, F31 and F32 to the F33 for
all architectures(x86_64,ARM,aarch64) and
variants(WS,cloud,server,silverblue,IoT).
The results can be submitted here[2]
As usual, we hang out on the #fedora-test-day, should you have questions.
[0] https://fedoraproject.org/wiki/Releases/33/ChangeSet
[1] https://fedoraproject.org/wiki/Test_Day:2020-09-21_F33_Upgrade_Test_Day
[2] https://testdays.fedorainfracloud.org/events/94
Happy Upgrading!
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
# F33 Blocker Review meeting
# Date: 2020-09-21
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 4 proposed Beta blockers, 4 proposed Beta freeze
exceptions and 3 proposed Final blockers to review, so we'll have a
Fedora 33 blocker review meeting on Monday. Unfortunately I'm not going
to be around to run it, but fortunately Ben Cotton has stepped up to do
it. Thanks Ben!
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/ .
** NEW ** - you can also now vote on bugs outside of review meetings!
For the Fedora 33 cycle we enabled a new voting system and have been
using it pretty heavily. 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.
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 much for the agenda, and I actually won't be available to run the
meeting either. If there is a desire to have the meeting, someone else
can volunteer to run it :)
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Hey Testers,
Friday, 2020-09-18 will be Fedora Media Writer Test Day[0]!
This Test Day will focus on Fedora Media Writer. Fedora Media Writer
is used for creating bootable flash drives on different operating
systems and architectures.
The tool is intended to be provided as the primary download option
since Fedora 25, with the aim of lowering the barrier for potential
users to try and install Fedora.
In this test day, we aim to test Fedora 33 pre-release boot-media
creation on Windows, OS X, and Fedora 31,32 and 33 specifically
targeting the creation of ARM-bootable media to see whether it's
working well enough and catch any remaining issues.
It's also pretty easy to join in: all you'll need is 4GB flash
drive/SD card (With all it's *data backed up*).
As always, the event will be in #fedora-test-day on Freenode IRC.
[0]: http://fedoraproject.org/wiki/Test_Day:2020-09-18_Fedora_Media_Writer
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
# F33 Blocker Review meeting
# Date: 2020-09-14
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 11 proposed Beta freeze exceptions and 3 proposed
Final blockers to review, so let's have a Fedora 33 blocker review
meeting on Monday! Above numbers are subject to change...
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
# Fedora Quality Assurance Meeting
# Date: 2020-09-14
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We didn't meet for a few weeks, 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. Fedora 33 status
3. Outstanding criteria proposals
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
Hello everyone,
I'd like to announce a new project of the QA team and an extension of the
BlockerBugs App [1]. The blocker and freeze exception proposals can now not
only be discussed during regular blocker review meetings [2], but also at
any time through discussion tickets hosted on Pagure [3]. So even if you
don't have time to participate in the meeting, you can still participate
and vote in those discussion tickets.
This will be mostly interesting to people who participated in blocker
review meetings in the past, but we hope we can attract new participants
this way. It is also very useful for package maintainers and developers,
because they can now easily provide feedback regarding a proposed blocker
or a freeze exception without attending a meeting at a particular time or
diluting a technical discussion in Bugzilla.
To participate, open the BlockerBugs App for a particular milestone (e.g.
F33 Beta [4]) and you'll see "Vote!" and "Discuss" links for
proposed/accepted blockers and freeze exceptions. Follow the links to see
tickets where you can express your opinion (which should ideally reflect
our release criteria [5]). You can vote according to the guide present at
[3], please read it carefully. A bot is following each ticket, updating the
voting summary, and accepting certain commands. Watching the Pagure repo
[3] also gives you the option to get notified about every new proposed
blocker/freeze exception.
We've been using these discussions for a week or two now (I apologize for a
late announcement) and so far our existing practice seems to be to vote for
proposals throughout the week using these discussion tickets, close those
which we can easily get enough votes and agree on, and discuss the
remainder during the next blocker review meeting. So the regular blocker
review meeting hasn't been replaced, but we use the discussion tickets to
cut down on the meeting length. We're still trying to figure out the best
approach to take here, so nothing is set in stone. The voting functionality
itself is also still in development, we'll try to provide new features and
improve the experience based on your feedback.
I'll be happy to answer questions, if there are any.
Thanks,
Kamil
Fedora QA
PS: Development credits go to Lukas Brabec, Frantisek Zatloukal, Tim Flink,
Josef Skladanka and Adam Williamson.
[1] https://qa.fedoraproject.org/blockerbugs/
[2] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[3] https://pagure.io/fedora-qa/blocker-review
[4] https://qa.fedoraproject.org/blockerbugs/milestone/33/beta/buglist
[5] https://fedoraproject.org/wiki/Fedora_Release_Criteria
Hey All,
Fedora is a community-driven project which means a lot of our users
use Fedora in multiple languages. The i18n Test day[0] is scheduled to
test changes that are coming in F33 along with
testing the regular GNOME apps in a multi-lingual environment.
This test day will also benefit from testers, testing the same in
Silverblue as well!
[0] http://fedoraproject.org/wiki/Test_Day:2020-09-08_I18N_Test_Day
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
# F33 Blocker Review meeting
# Date: ** 2020-09-08 ** (Tuesday!)
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 4 proposed Beta blockers, 1 proposed Final blocker
and 2 proposed Beta freeze exceptions to review, so let's have a Fedora
33 blocker review meeting on ** TUESDAY **! Monday is a holiday in
North America, so many of the regular attendees would be missing. For
that reason I'm scheduling the meeting for one day later than usual,
on Tuesday.
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 *TUESDAY*!
[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. It's a
holiday in North America, so many folks who would usually be present
will be off. I'll make sure we follow up the outstanding criteria
proposals on the mailing list(s).
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net