Hi folks!
So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
networking criteria.
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
Using the default network configuration tools for the console and for
release-blocking desktops, it must be possible to establish a working
connection to common OpenVPN, openconnect-supported and vpnc-supported
VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are
many different VPN server applications and configurations, blocker
reviewers must use their best judgment in determining whether
violations of this criterion are likely to be encountered commonly
enough to block a release, and if so, at which milestone. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Hello everyone,
A new version of default time of day wallpaper for Fedora 35 is
available for testing and ready for the applications like Software needed
to display the availability of Fedora 35.
Link: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0d3eae84ae
Let know if there are some issues needed to address before the final
freeze on October 4.
Regards,
--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
==============================================
#fedora-meeting-2: Workstation WG (2021-09-14)
==============================================
Meeting started by cmurf at 05:01:56 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-09-18/workstation.2…
.
Meeting summary
---------------
* Rollcall (cmurf, 05:02:10)
* present: Allan, Neal, Kalev, Matthias, Tomas, Michael, Jens, Owen,
Felipe (cmurf, 05:02:12)
* regrets: Chris (cmurf, 05:02:14)
* present guests: Luna Jernberg (bittin) (cmurf, 05:02:16)
* Approval of September 7 minutes (cmurf, 05:02:18)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-09-08/workstation.2…
(cmurf, 05:02:20)
* AGREED: Approved (cmurf, 05:02:22)
* Announcements, follow-ups, status reports (cmurf, 05:02:24)
* Michael: In Fedora 35 gnome-initial-setup is in a pretty bad state
(everything is broken). (cmurf, 05:02:26)
* Toolbox is broken in Fedora 35 as well. (cmurf, 05:02:32)
* Fedora 35 milestones (cmurf, 05:02:34)
* ACTION: Owen to enable the missing fedora-third-party-refresh onboot
service for silverblue. Tomas to help with testing. (cmurf,
05:02:40)
* We've decided to disable parental controls in gnome-initial-setup.
(cmurf, 05:02:44)
* ACTION: Allan to file a ticket against gnome-initial-setup for FE;
Kalev to disable it in gnome-initial-setup. (cmurf, 05:02:46)
* GNOME Software 41 declares Fedora RPMs "unsafe" (cmurf, 05:02:48)
* LINK: https://pagure.io/fedora-workstation/issue/244 (cmurf,
05:02:50)
* Open Floor (cmurf, 05:03:06)
Meeting ended at 05:05:23 UTC.
Action Items
------------
* Owen to enable the missing fedora-third-party-refresh onboot service
for silverblue. Tomas to help with testing.
* Allan to file a ticket against gnome-initial-setup for FE; Kalev to
disable it in gnome-initial-setup.
Action Items, by person
-----------------------
* **UNASSIGNED**
* Owen to enable the missing fedora-third-party-refresh onboot service
for silverblue. Tomas to help with testing.
* Allan to file a ticket against gnome-initial-setup for FE; Kalev to
disable it in gnome-initial-setup.
People Present (lines said)
---------------------------
* cmurf (34)
* zodbot (7)
* : (0)
* Neal (0)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: http://wiki.debian.org/MeetBot
---------- Forwarded message ---------
From: Luna Jernberg <droidbittin(a)gmail.com>
Date: Thu, Sep 16, 2021 at 2:30 PM
Subject: Fwd: Fedora rawhide compose report: 20210916.n.0 changes
To: Martin Jernberg <droidbittin(a)gmail.com>, Luna Jernberg <
bittin(a)fedoraproject.org>
---------- Forwarded message ---------
From: Luna Jernberg <droidbittin(a)gmail.com>
Date: Thu, Sep 16, 2021 at 2:30 PM
Subject: Re: Fedora rawhide compose report: 20210916.n.0 changes
To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>,
For testing and quality assurance of Fedora releases <
test(a)lists.fedoraproject.org>
g-i-s is still broken in the Workstation iso for Rawhide today btw just
fyi, crashing after install in a Virtualbox VM for me
On Thu, Sep 16, 2021 at 2:20 PM Kalev Lember <kalevlember(a)gmail.com> wrote:
> On Thu, Sep 16, 2021 at 2:14 PM Fabio Valentini <decathorpe(a)gmail.com>
> wrote:
>
>> On Thu, Sep 16, 2021 at 1:09 PM Fedora Rawhide Report
>> <rawhide(a)fedoraproject.org> wrote:
>> > ===== ADDED PACKAGES =====
>> > Package: atkmm2.36-2.36.1-1.fc36
>> > Summary: C++ interface for the ATK library
>> > RPMs: atkmm2.36 atkmm2.36-devel atkmm2.36-doc
>> > Size: 1.35 MiB
>>
>> (...)
>>
>> > Package: glibmm2.68-2.68.1-1.fc36
>> > Summary: C++ interface for the GLib library
>> > RPMs: glibmm2.68 glibmm2.68-devel glibmm2.68-doc
>> > Size: 12.65 MiB
>> >
>> > Package: gtkmm4.0-4.4.0-1.fc36
>> > Summary: C++ interface for the GTK+ library
>> > RPMs: gtkmm4.0 gtkmm4.0-devel gtkmm4.0-doc
>> > Size: 17.64 MiB
>> >
>> > Package: pangomm2.48-2.48.1-1.fc36
>> > Summary: C++ interface for Pango
>> > RPMs: pangomm2.48 pangomm2.48-devel pangomm2.48-doc
>> > Size: 1.26 MiB
>>
>> Is there a reason why these compat packages are done "the wrong way
>> round"?
>> They were requested with exceptions to the review process, but that
>> exception only applies to requesting versioned compat packages for the
>> *old* version, not the other way round ...
>>
>
> Sure, there's a good reason! I wanted to keep the same pattern as gtk has,
> so that there's gtk3 and matching gtkmm3.0, and gtk4 and matching gtkmm4.0.
>
> They are all long-lived parallel installable packages and most stuff is
> going to be using the "old" gtkmm3.0 still for a number of years to come.
>
> Doing it this way also makes it much easier to add the new packages to F34
> where I don't want to be undertaking large package renaming.
>
> --
> Kalev
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>