On Fri, Aug 31, 2018 at 05:57:57PM +0200, Adam Samalik wrote:
> > I don't think we should use "rawhide" to mean "rolling updates", because it
> > also has the implication of "project devel stream".
> Just to make sure we're on the same page: I was talking about specifying an
> EOL field, not a
On Fri, Aug 31, 2018 at 5:01 PM Matthew Miller
wrote:
> On Wed, Aug 29, 2018 at 10:26:29AM +0200, Adam Samalik wrote:
> > > Would it be necessary for us to pick one or the other here? IOW,
> > > whether the maintainer picked a specific date or a release, the EOL
> > > would resolve to a date. If
On Wed, Aug 29, 2018 at 10:26:29AM +0200, Adam Samalik wrote:
> > Would it be necessary for us to pick one or the other here? IOW,
> > whether the maintainer picked a specific date or a release, the EOL
> > would resolve to a date. If they pick none, or explicitly choose
> > 'rawhide,' then the
On Wed, Aug 29, 2018 at 4:35 AM Adam Samalik wrote:
> On Tue, Aug 28, 2018 at 6:44 PM Paul Frields wrote:
>>
>> On Wed, Aug 22, 2018 at 7:26 AM Adam Samalik wrote:
>> > == Approaches
>> >
>> > Option 1: The current, yet unfinished approach
>> >
>> > We specify an EOL (end of life) date for each
On Tue, Aug 28, 2018 at 6:44 PM Paul Frields wrote:
> On Wed, Aug 22, 2018 at 7:26 AM Adam Samalik wrote:
> > == Approaches
> >
> > Option 1: The current, yet unfinished approach
> >
> > We specify an EOL (end of life) date for each stream branch of
> individual packages. This is done when
On Wed, Aug 22, 2018 at 7:26 AM Adam Samalik wrote:
> == Approaches
>
> Option 1: The current, yet unfinished approach
>
> We specify an EOL (end of life) date for each stream branch of individual
> packages. This is done when requesting a new stream branch for a package [2]
> by passing "--sl
On Wed, Aug 22, 2018 at 5:48 PM Owen Taylor wrote:
> What are the possibilities for how a stream is maintained? The cases I can
> think of:
>
> * Indefinite - rolling forward with upstream - "master" "stable" etc.
> * Tied to an upstream version and it's EOL - a "2.1" stream of django
>
*
What are the possibilities for how a stream is maintained? The cases I can
think of:
* Indefinite - rolling forward with upstream - "master" "stable" etc.
* Tied to an upstream version and it's EOL - a "2.1" stream of django
* [less common] tied to a particular version of Fedora - the "29"
