On Sun, Sep 20, 2020 at 1:47 PM Kevin Fenzi wrote:
> > Tangent nit-pick... Once an update has been created for a branch, why not
> > at least allow it to go to stable? Seeing my packages stuck in testing
> for
> > eternity bothers my OCD until I push enough updates I don't see it
> anymore.
>
>
On 20. 09. 20 20:45, Kevin Fenzi wrote:
But also because it doesn't really make sense to me. I can imagine a case
when a bug in Fedora N can be fixed by adding a new package (for example
when we accidentally introduce a new dependency) and I don't understand why
Wouldn't that be caught in
On Sat, Sep 19, 2020 at 03:11:39PM -0500, Richard Shaw wrote:
> On Fri, Sep 18, 2020 at 5:03 PM Ben Cotton wrote:
>
> > On Fri, Sep 18, 2020, 17:03 Miro Hrončok wrote:
> >
> >>
> >> So, my question is: Should we fix the document to describe the long
> >> standing
> >> practice more
On Fri, Sep 18, 2020 at 11:02:26PM +0200, Miro Hrončok wrote:
> Hello,
>
> As many of you know, Fedora has an EOL policy that roughly tl;drs to:
>
> "Fedora N goes to End of Life 4 weeks after Fedora N+2 Final Release (GA)."
>
> https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle
>
> The
On Fri, Sep 18, 2020 at 5:03 PM Ben Cotton wrote:
> On Fri, Sep 18, 2020, 17:03 Miro Hrončok wrote:
>
>>
>> So, my question is: Should we fix the document to describe the long
>> standing
>> practice more understandably, or should we change the practice to allow
>> new
>> dist-git branches
On Fri, Sep 18, 2020, 17:03 Miro Hrončok wrote:
>
> So, my question is: Should we fix the document to describe the long
> standing
> practice more understandably, or should we change the practice to allow
> new
> dist-git branches until the actual EOL?
>
I'm in favor of allowing new branches
Hello,
As many of you know, Fedora has an EOL policy that roughly tl;drs to:
"Fedora N goes to End of Life 4 weeks after Fedora N+2 Final Release (GA)."
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle
The document also says:
> Branches for new packages in the SCM are not allowed for
