# F28 Blocker Review meeting
# Date: 2018-04-09
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 6 proposed blockers and 2 proposed freeze exception
issues for Final to review, so let's have a review meeting on Monday.
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 F28 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 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
PR in: https://pagure.io/fedora-comps/pull-request/248
This came out of various discussions; see https://pagure.io/workstation-ostree-config/pull-request/74
and in particular: https://pagure.io/workstation-ostree-config/pull-request/74#comment-47627
The high level goal here is to make Workstation more container oriented by default,
reducing the delta from Atomic.
In particular I'd like to flesh out the "pet/dev container" pattern discussed in various
places and encourage people to do that rather than installing things in their root filesystem
by default. It's a tremendous change - it was painful for me at first. But there are a lot of
compelling advantages.
By having e.g. `podman` (and `docker` for people used to that) installed by default we
take a step towards encouraging that by default.
A simple example here: At some point `fpaste` was added to @standard in comps and
hence installed on Workstation by default. It's small and harmless, but those types of things pile up.
Instead, `fpaste` is exactly the kind of thing that should live in your dev container. Along
with several other things from @standard like tcpdump, traceroute, and telnet.
And gcc, golang, cargo, ansible, pip, etc.
As a reminder, the Fedora Atomic Workstation SIG will have it's bi-weekly
meeting today
Time: 9:00am US/Eastern - 13:00utc.
Place: Freenode #fedora-meeting-2