On Mon, Feb 28, 2022 at 12:37 PM Adam Williamson
wrote:
>
> So, uh, we sorta forgot about this. Kamil approved this draft, but
> nobody else gave any feedback on it. This topic is still relevant and
> we have a proposed VPN blocker today, so...any more feedback on this
> draft?
I think it's sound
On Fri, 2020-08-28 at 16:59 -0700, Adam Williamson wrote:
> On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote:
> > 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
On Sat, Aug 29, 2020 at 1:59 AM Adam Williamson
wrote:
> On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote:
> > 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
On Sat, Aug 29, 2020 at 1:57 AM Adam Williamson
wrote:
> On Thu, 2020-08-27 at 10:06 -0600, Chris Murphy wrote:
> > On Fri, Aug 21, 2020 at 6:11 PM Adam Williamson
> > wrote:
> > >
> > > Basic networking
> > >
> > > It must be possible to establish both IPv4 and IPv6 network connection
On Fri, Aug 28, 2020 at 7:52 PM Chris Murphy wrote:
> The IPP Everywhere specification requires clients to support DNS-SD
> (mDNS is part of that) or WS-Discovery. Printers are required to
> support both DNS-SD and WS-Discovery. Avahi and systemd-resolved
> support DNS-SD, functionally equating D
[Sorry for the double post, somewhere along the way desktop@ and kde@
were dropped, so I'm re-adding them and that means double post for
test@ and devel@.]
Re: add working mDNS to the criterion
The IPP Everywhere specification requires clients to support DNS-SD
(mDNS is part of that) or WS-Disco
On Fri, Aug 28, 2020 at 5:56 PM Adam Williamson
wrote:
>
> On Thu, 2020-08-27 at 10:06 -0600, Chris Murphy wrote:
> > On Fri, Aug 21, 2020 at 6:11 PM Adam Williamson
> > wrote:
> > >
> > > Basic networking
> > >
> > > It must be possible to establish both IPv4 and IPv6 network connectio
On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote:
> 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
On Thu, 2020-08-27 at 10:06 -0600, Chris Murphy wrote:
> On Fri, Aug 21, 2020 at 6:11 PM Adam Williamson
> wrote:
> >
> > Basic networking
> >
> > It must be possible to establish both IPv4 and IPv6 network connections
> > using DHCP and static addressing. The default network configura
On Thu, Aug 27, 2020 at 6:08 PM Chris Murphy
wrote:
> What about mDNS?
>
> Something to the effect that if it's installed and enabled by a
> default package set for an edition, it should work (resolve and
> respond). That means it would apply to Workstation and KDE. It
> wouldn't apply to Cloud,
On Thu, Aug 27, 2020 at 8:37 PM Adam Williamson
wrote:
> > > 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
On Thu, 2020-08-27 at 15:44 +0200, Kamil Paral wrote:
> On Sat, Aug 22, 2020 at 2:12 AM Adam Williamson
> wrote:
>
> > === Network requirements ===
> >
> > Each of these requirements apply to both installer and installed system
> > environments. For any given installer environment, the 'default
On Fri, Aug 21, 2020 at 6:11 PM Adam Williamson
wrote:
>
> 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 wor
On Sat, Aug 22, 2020 at 2:12 AM Adam Williamson
wrote:
> === 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 install
On Tue, 2020-08-25 at 16:11 -0700, Adam Williamson wrote:
> On Tue, 2020-08-25 at 15:50 -0700, Michel Alexandre Salim wrote:
> > On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote:
> > > VPN connections
> > >
> > >
> > >
> > > Using the default network configuration tools for the
On Tue, 2020-08-25 at 15:50 -0700, Michel Alexandre Salim wrote:
> On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote:
> > VPN connections
> >
> >
> >
> > Using the default network configuration tools for the console and for
> >
> > release-blocking desktops, it must be possible
On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote:
> 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
That all sounds reasonable to me. Does wifi fall into this as well?
Stephen
On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote:
> 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
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 V
19 matches
Mail list logo
