sgallagh and I both noticed that the release criteria do not currently
include any requirements around Edition branding or installer
customizations. We think they probably should. Thus, we're proposing
the following new criteria. They would be in a new section for each
page, something like "Edition requirements" or something like that,
probably with a brief explanation of what "Editions" are outside of any
specific criterion text.
For Beta:
== Installer customization ==
For each Edition, all significant functional customization of installer
behavior that are intended to be a part of that Edition must take
effect on that Edition's installable release-blocking images.
footnote: 'Significant functional?': significant functional
customization would usually include, for e.g., changes to the default
filesystem and firewall configuration. The WG or SIG responsible for
each Edition has the definitive say on what is or is not considered a
'significant functional customization' for that Edition.
For Final:
== Self-identification ==
For each Edition, the installer must be clearly identified as that
Edition in all of that Edition's installable release-blocking images.
Also, for any deployment of that Edition in accordance with the rest of
these criteria, the relevant fields in {{filename|/etc/os-release}}
must include the correct Edition name.
Thoughts, comments, suggestions, flames? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2018-01-31 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
Hi cloud team,
I'm Alberto from the marketing team,
Talking points are key highlights of the new release. They should be
compelling, but they will not necessarily be comprehensive. There are
different types of talking points for different types of people:
general desktop users/everyone, developers, and sysadmins. For the
Fedora 28 cycle, we will also have talking points to address some of
the Spins. They are meant to provide a short, effective answer to the
question, "What cool stuff is in the latest release of Fedora?"
Each cycle, the Marketing team compiles a short list of approximately
three talking points for each of these audiences for the upcoming
release.
So, What is new from the Cloud Team side??
If you have a talking point that you feel meets the criteria found on
the talking points SOP page at
https://fedoraproject.org/wiki/Talking_points_SOP,
Best Regards
--
Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2018-01-24 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2018-01-17 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2018-01-10 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
# F28 Blocker Review meeting
# Date: 2018-01-08
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have six proposed blockers for Fedora 28 Beta, so let's
have a review meeting on Monday.
If you have time over the 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 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 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