Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Richard W.M. Jones
On Thu, Apr 04, 2019 at 09:24:13AM -0400, Stephen Gallagher wrote: > On Wed, Apr 3, 2019 at 11:46 AM Adam Samalik wrote: > > > > Some modules now use "latest", "stable", or "master" as stream names for > > various different things. It's quite confusing and I want to fix that. > > > > Without

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Adam Samalik
On Thu, Apr 4, 2019 at 3:59 PM Matthew Miller wrote: > On Thu, Apr 04, 2019 at 09:24:13AM -0400, Stephen Gallagher wrote: > > > Without naming them, I see two different use cases: > > > 1/ "for end users" — rolling stream meant for end users to consume, > likely used in projects without

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Adam Samalik
On Thu, Apr 4, 2019 at 3:55 PM Matthew Miller wrote: > On Thu, Apr 04, 2019 at 09:25:36AM -0400, Stephen Gallagher wrote: > > > > So the question is, do people agree there are two? Or just one? Or > more? > > > Upstreams aren't consistent. There's a good argument for making our > branches > > >

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Matthew Miller
On Thu, Apr 04, 2019 at 09:24:13AM -0400, Stephen Gallagher wrote: > > Without naming them, I see two different use cases: > > 1/ "for end users" — rolling stream meant for end users to consume, likely > > used in projects without traditional versioning scheme, or for the latest > > version that

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Matthew Miller
On Thu, Apr 04, 2019 at 09:25:36AM -0400, Stephen Gallagher wrote: > > > So the question is, do people agree there are two? Or just one? Or more? > > Upstreams aren't consistent. There's a good argument for making our branches > > match the pratices of upstreams -- but when two different upstreams

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Stephen Gallagher
On Thu, Apr 4, 2019 at 9:23 AM Matthew Miller wrote: > > On Wed, Apr 03, 2019 at 05:44:43PM +0200, Adam Samalik wrote: > > So the question is, do people agree there are two? Or just one? Or more? > > Upstreams aren't consistent. There's a good argument for making our branches > match the pratices

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Stephen Gallagher
On Wed, Apr 3, 2019 at 11:46 AM Adam Samalik wrote: > > Some modules now use "latest", "stable", or "master" as stream names for > various different things. It's quite confusing and I want to fix that. > > Without naming them, I see two different use cases: > > 1/ "for end users" — rolling

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Matthew Miller
On Wed, Apr 03, 2019 at 05:44:43PM +0200, Adam Samalik wrote: > So the question is, do people agree there are two? Or just one? Or more? Upstreams aren't consistent. There's a good argument for making our branches match the pratices of upstreams -- but when two different upstreams think different

Modularity question for packagers about rolling/latest/stable/master streams

2019-04-03 Thread Adam Samalik
Some modules now use "latest", "stable", or "master" as stream names for various different things. It's quite confusing and I want to fix that. Without naming them, I see two different use cases: 1/ "for end users" — rolling stream meant for end users to consume, likely used in projects without