No, we did NOT do that.
A quick search on the devel list archives shows that F19 was released in July
2013:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SSLJL6ZJC7M7TAOPNHJY7UAS7MA66PMR/
...and EOL'd on in January 2015:
Peter Robinson wrote:
> So going back to memory of what we did in the F-21 cycle, we EOLed
> F-19 at the 13 months line and then F-20 continued until a month after
> F-22 was out.
No, we did not! F19 was supported until a month after F21 was released:
On Wed, Nov 28, 2018 at 08:45:55AM +, Peter Robinson wrote:
> > If F31 is delayed by 6 months and F30 is supported for 6 months longer,
> > does it mean F29 *also* automatically gets a longer cycle since it by
> > policy becomes EOL when F31 is out + 1 month?
> > Can we EOL F29 6 months before
On 28/11/2018 08:45, Peter Robinson wrote:
On Wed, Nov 28, 2018 at 7:14 AM Kalev Lember wrote:
If F31 is delayed by 6 months and F30 is supported for 6 months longer,
does it mean F29 *also* automatically gets a longer cycle since it by
policy becomes EOL when F31 is out + 1 month?
Can we
On Wed, Nov 28, 2018 at 7:14 AM Kalev Lember wrote:
>
> If F31 is delayed by 6 months and F30 is supported for 6 months longer,
> does it mean F29 *also* automatically gets a longer cycle since it by
> policy becomes EOL when F31 is out + 1 month?
>
> Can we EOL F29 6 months before F31 is out to
If F31 is delayed by 6 months and F30 is supported for 6 months longer,
does it mean F29 *also* automatically gets a longer cycle since it by
policy becomes EOL when F31 is out + 1 month?
Can we EOL F29 6 months before F31 is out to not have *two* long term
branches to maintain?
--
Kalev
