Re: Proposing new release criteria

2019-09-30 Thread Dusty Mabe
On 8/29/19 10:33 AM, Dusty Mabe wrote: > I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This is > a suggestion > after we found podman can't pull containers from a registry in f31 [1]. >

Re: Proposing new release criteria

2019-08-30 Thread Clement Verna
> I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This is > a suggestion > after we found podman can't pull containers from a registry in f31 [1]. > > New section for Containers and Contain

Re: Proposing new release criteria

2019-08-30 Thread Dusty Mabe
On 8/30/19 9:36 AM, Kamil Paral wrote: > On Thu, Aug 29, 2019 at 4:33 PM Dusty Mabe > wrote: > > I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This

Re: Proposing new release criteria

2019-08-30 Thread Kamil Paral
On Thu, Aug 29, 2019 at 4:33 PM Dusty Mabe wrote: > I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This > is a suggestion > after we found podman can't pull containers from a registry in f3

Re: Proposing new release criteria

2019-08-29 Thread Daniel Walsh
On 8/29/19 3:15 PM, Dusty Mabe wrote: > > On 8/29/19 2:36 PM, Daniel Walsh wrote: >> On 8/29/19 2:16 PM, Mairi Dulaney wrote: >>> On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe: I don't know the formal process for proposal but here is a shot at a bare minimum start for try

Re: Proposing new release criteria

2019-08-29 Thread Dusty Mabe
On 8/29/19 2:36 PM, Daniel Walsh wrote: > On 8/29/19 2:16 PM, Mairi Dulaney wrote: >> On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe: >>> I don't know the formal process for proposal but here is a shot at a bare >>> minimum >>> start for trying to add containers to the existing release

Re: Proposing new release criteria

2019-08-29 Thread Daniel Walsh
On 8/29/19 2:16 PM, Mairi Dulaney wrote: > On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe: >> I don't know the formal process for proposal but here is a shot at a bare >> minimum >> start for trying to add containers to the existing release criteria. This is >> a suggestion >> after we

Re: Proposing new release criteria

2019-08-29 Thread Daniel Walsh
On 8/29/19 2:28 PM, Adam Williamson wrote: > On Thu, 2019-08-29 at 20:15 +0200, Julen Landa Alustiza wrote: >> Could we go on a more generic fashion? >> >> Something like "Supported container engines must work on their basic >> features on all the blocker deliverables were they are installed by >>

Re: Proposing new release criteria

2019-08-29 Thread Adam Williamson
On Thu, 2019-08-29 at 20:15 +0200, Julen Landa Alustiza wrote: > Could we go on a more generic fashion? > > Something like "Supported container engines must work on their basic > features on all the blocker deliverables were they are installed by > default" > > Our supported engines are, podman?

Re: Proposing new release criteria

2019-08-29 Thread Mairi Dulaney
On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe: > I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This is > a suggestion > after we found podman can't pull containers from a regist

Re: Proposing new release criteria

2019-08-29 Thread Julen Landa Alustiza
Could we go on a more generic fashion? Something like "Supported container engines must work on their basic features on all the blocker deliverables were they are installed by default" Our supported engines are, podman? cri-o? On August 29, 2019 6:40:21 PM GMT+02:00, Matthew Miller wrote: >O

Re: Proposing new release criteria

2019-08-29 Thread Matthew Miller
On Thu, Aug 29, 2019 at 11:45:44AM -0400, Dusty Mabe wrote: > Certainly anywhere where podman is shipped on media. Does podman ship in the > server DVD? yes [1] > It looks like workstation also ships it if I'm reading the logs [2] correctly. Yeah, it's needed for Toolbox, which is a vital feature

Re: Proposing new release criteria

2019-08-29 Thread Dusty Mabe
On 8/29/19 11:13 AM, Adam Williamson wrote: > On Thu, 2019-08-29 at 10:33 -0400, Dusty Mabe wrote: >> I don't know the formal process for proposal > > Congratulations, you found it - mail this list, ideally including at > least one of the strings 'criter' or 'propos'. :P > >> but here is a sho

Re: Proposing new release criteria

2019-08-29 Thread Adam Williamson
On Thu, 2019-08-29 at 10:33 -0400, Dusty Mabe wrote: > I don't know the formal process for proposal Congratulations, you found it - mail this list, ideally including at least one of the strings 'criter' or 'propos'. :P > but here is a shot at a bare minimum > start for trying to add containers t

Re: Proposing new release criteria

2019-08-29 Thread Dusty Mabe
> I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. There is at least one deliverable that delivers podman in the image (Silverblue). Silverblue isn't release blocking. I don't know if there

Proposing new release criteria

2019-08-29 Thread Dusty Mabe
I don't know the formal process for proposal but here is a shot at a bare minimum start for trying to add containers to the existing release criteria. This is a suggestion after we found podman can't pull containers from a registry in f31 [1]. New section for Containers and Container tools: - A