Fedora Linux 37 is EOL

[Tomas Hrcka]

Hello all,

Fedora Linux 37 has gone end of life for updates and support on 2023-12-05.
No more updates of any kind, including security updates or security
announcements, will be available for Fedora Linux 37 after the said
date. All the updates of Fedora Linux 37 being pushed to stable will be
stopped as well.

Fedora Linux 38 will continue to receive updates until approximately
one month after the release of Fedora Linux 40. The maintenance
schedule of Fedora Linux releases is documented on the Fedora Project
wiki [1]. The Fedora Project wiki also contains instructions[2] on how
to upgrade from a previous release of Fedora Linux to a version
receiving updates.

This email template is also in https://pagure.io/releng if you wish to
propose improvements or changes to it.

Regards,
Tomas Hrcka
Fedora Release Engineering

[1] -
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedul...
[2] - https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
[3] - https://pagure.io/releng

[Jens-Ulrik Petersen]

(Replying to devel list)

Can someone please update
https://docs.fedoraproject.org/en-US/releases/eol/#_unsupported_fedora_linux...
to correct the EOL date for F37 to 5th Dec?

Or should I open a releng ticket for that?

Thanks!
Jens

[Miroslav Suchý]

Dne 07. 01. 24 v 6:15 Jens-Ulrik Petersen napsal(a):
> (Replying to devel list)
>
> Can someone please update https://docs.fedoraproject.org/en-US/releases/eol/#_unsupported_fedora_linux...
> to correct the EOL date for F37 to 5th Dec?
>
> Or should I open a releng ticket for that?

PR is enough (in the upper right corner is edit button). And there is already one

https://pagure.io/fedora-pgm/pgm_docs/pull-request/62

Someone just need to merge this.

[Sandro]

On 05-12-2023 18:45, Tomas Hrcka wrote:
> Fedora Linux 37 has gone end of life for updates and support on 2023-12-05.
> No more updates of any kind, including security updates or security
> announcements, will be available for Fedora Linux 37 after the said
> date. All the updates of Fedora Linux 37 being pushed to stable will be
> stopped as well.

As part of the EOL tasks all bugs open for F37 receive an EOL notice, 
first, and sometime later they will change status to CLOSED | EOL, 
unless the version is changed.

It seems the first step (notification) happened, but the second step 
(closing) has not completed. IIRC, I saw some bugs being closed, but I 
also see a lot of F37 bugs still open [1].

Is that an oversight or did something go wrong during the procedure? I 
cc'ed Aoife, who appears to have run the first step. I'm happy to open a 
ticket if required.

[1] https://da.gd/121FsB

-- Sandro

[Aoife Moloney]

I'll get the EOL-close script running again, it kept timing out so I
thought it was finished but clearly not - my mistake and apologies :-/

The PR for the EOL date cannot be merged as there are conflicts so I will
just close that one as the F37 EOL date is on the main page, but I forgot
the navigation bar update which is done separately. Will resolve that now.

On Mon, Jan 8, 2024 at 12:02 PM Sandro  wrote:
> On 05-12-2023 18:45, Tomas Hrcka wrote:
> > Fedora Linux 37 has gone end of life for updates and support on
>
> 2023-12-05.
> > No more updates of any kind, including security updates or security
> > announcements, will be available for Fedora Linux 37 after the said
> > date. All the updates of Fedora Linux 37 being pushed to stable will be
> > stopped as well.
>
> As part of the EOL tasks all bugs open for F37 receive an EOL notice,
> first, and sometime later they will change status to CLOSED | EOL,
> unless the version is changed.
>
> It seems the first step (notification) happened, but the second step
> (closing) has not completed. IIRC, I saw some bugs being closed, but I
> also see a lot of F37 bugs still open [1].
>
> Is that an oversight or did something go wrong during the procedure? I
> cc'ed Aoife, who appears to have run the first step. I'm happy to open a
> ticket if required.
>
> [1] https://da.gd/121FsB
>
> -- Sandro
>
> --
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Adam Williamson]

On Mon, 2024-01-08 at 16:10 +0000, Aoife Moloney wrote:
> I'll get the EOL-close script running again, it kept timing out so I
> thought it was finished but clearly not - my mistake and apologies :-/

Just so folks are aware, the EOL closure uses a script:
https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/closebugs/fedora_bz.py
which runs bug-by-bug - so it comments on, or closes, one bug at a
time. This means it takes a very long time to do the ~2-3k bugs that
are typically commented-on then closed at EOL time.

Doing it this way was Ben's preference (he wanted to be able to see
that every bug was updated and get a notice from the script for any
single bug change that failed), but if it causes problems for Aoife we
can have it mass-update bugs instead, since Bugzilla and its API allow
that (now, they probably didn't when the predecessors to this script
were written). I'll just have to check with the BZ admin whether
there's any upper limit on how many bugs you can request a mass change
to at once.

[Sandro]

On 08-01-2024 17:16, Adam Williamson wrote:
> On Mon, 2024-01-08 at 16:10 +0000, Aoife Moloney wrote:
> > I'll get the EOL-close script running again, it kept timing out so I
> > thought it was finished but clearly not - my mistake and apologies :-/
>
> Just so folks are aware, the EOL closure uses a script:
> https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/closebugs/fedora_bz.py
> which runs bug-by-bug - so it comments on, or closes, one bug at a
> time. This means it takes a very long time to do the ~2-3k bugs that
> are typically commented-on then closed at EOL time.
>
> Doing it this way was Ben's preference (he wanted to be able to see
> that every bug was updated and get a notice from the script for any
> single bug change that failed), but if it causes problems for Aoife we
> can have it mass-update bugs instead, since Bugzilla and its API allow
> that (now, they probably didn't when the predecessors to this script
> were written). I'll just have to check with the BZ admin whether
> there's any upper limit on how many bugs you can request a mass change
> to at once.

I just noticed that some bugs with version '37' were still open while 
others were already closed.

I think it makes perfect sense to do a mass update to the extend 
possible to have this process finish quicker. It's fairly easy to query 
for bugs that may have been missed afterwards. That's essentially what I 
did with my query.

You may also have to check with mail admins, because it might break the 
levees of the mail river doing a mass update, I could imagine.

-- Sandro

[Ben Cotton]

On 08-01-2024 17:16, Adam Williamson wrote:
> Doing it this way was Ben's preference (he wanted to be able to see
> that every bug was updated and get a notice from the script for any
> single bug change that failed),

Historically, the script ran much faster than Bugzilla, which meant
after a while, we'd start getting timeouts. This is why there are
pauses built into the script. A few years ago, the performance of
Bugzilla improved greatly, but I never felt like exploring where the
boundaries are. Updating all matching bugs in one transaction is still
probably going to result in timeouts, but smaller chunks should work
well enough. Of course, that means a transient failure could cause
many bugs to need to be re-run instead of just one. That's not to say
it can't be done, but it was never a priority for me.

On Mon, Jan 8, 2024 at 11:30 AM Sandro  wrote:
> I just noticed that some bugs with version '37' were still open while
> others were already closed.

I'm not saying that's what happened here, but it's not uncommon to see
bugs that are closed EOL get re-opened but not have an updated
version. For a long time, I never checked that when putting the bug
count lists in the Friday's Fedora Facts posts. The first time I did,
there were hundreds of bugs across several EOL releases. :-)

[Adam Williamson]

On Mon, 2024-01-08 at 13:57 -0500, Ben Cotton wrote:
> On 08-01-2024 17:16, Adam Williamson wrote:
> > Doing it this way was Ben's preference (he wanted to be able to see
> > that every bug was updated and get a notice from the script for any
> > single bug change that failed),
>
> Historically, the script ran much faster than Bugzilla, which meant
> after a while, we'd start getting timeouts. This is why there are
> pauses built into the script. A few years ago, the performance of
> Bugzilla improved greatly, but I never felt like exploring where the
> boundaries are. Updating all matching bugs in one transaction is still
> probably going to result in timeouts, but smaller chunks should work
> well enough.

If Bugzilla is engineered *at all* sanely, it should be much less work
for it to process a single request to do the same thing to 500 bugs
than it is to process 500 individual requests to do the same thing to a
single bug. There probably *is* a limit on the number of bugs you can
request changes to at once, but it should be simple enough to find out
what that ceiling is and work in batches below it.

[Vít Ondruch]

Any update? This ticket is still open:

https://bugzilla.redhat.com/show_bug.cgi?id=2235331

Vít

Dne 08. 01. 24 v 17:10 Aoife Moloney napsal(a):
> I'll get the EOL-close script running again, it kept timing out so I 
> thought it was finished but clearly not - my mistake and apologies :-/
>
> The PR for the EOL date cannot be merged as there are conflicts so I 
> will just close that one as the F37 EOL date is on the main page, but 
> I forgot the navigation bar update which is done separately. Will 
> resolve that now.
>
> On Mon, Jan 8, 2024 at 12:02 PM Sandro  wrote:
> On 05-12-2023 18:45, Tomas Hrcka wrote:
> > Fedora Linux 37 has gone end of life for updates and support on
> 2023-12-05.
> > No more updates of any kind, including security updates or security
> > announcements, will be available for Fedora Linux 37 after the said
> > date. All the updates of Fedora Linux 37 being pushed to stable
> will be
> > stopped as well.
>
>
> As part of the EOL tasks all bugs open for F37 receive an EOL notice,
> first, and sometime later they will change status to CLOSED | EOL,
> unless the version is changed.
>
> It seems the first step (notification) happened, but the second step
> (closing) has not completed. IIRC, I saw some bugs being closed,
> but I
> also see a lot of F37 bugs still open [1].
>
> Is that an oversight or did something go wrong during the
> procedure? I
> cc'ed Aoife, who appears to have run the first step. I'm happy to
> open a
> ticket if required.
>
> [1] https://da.gd/121FsB
>
> -- Sandro
>
> --
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
>
>
> --
>
> Aoife Moloney
>
> Fedora Operations Architect
>
> Fedora Project
>
> Matrix: @amoloney:fedora.im http://fedora.im
>
> IRC: amoloney
>
> --
> _______________________________________________
> devel mailing list [e-mail]
> To unsubscribe send an email [e-mail]
> Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue

[Sandro]

On 15-01-2024 09:52, Vít Ondruch wrote:
> Any update? This ticket is still open:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2235331

I believe the script is chugging along. I've seen a few more bugs being 
closed the last couple of days.

-- Sandro

[Aoife Moloney]

Ok I have re-ran the script again, this time it finished so I believe all
F37 bugs are now closed <crosses fingers>. If you come across any open
ones, do let me know and I will re-run the autoclose script.

Thanks!
Aoife

On Mon, Jan 15, 2024 at 8:22 PM Sandro  wrote:
> On 15-01-2024 09:52, Vít Ondruch wrote:
> > Any update? This ticket is still open:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2235331
>
> I believe the script is chugging along. I've seen a few more bugs being
> closed the last couple of days.
> -- Sandro
>
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Vít Ondruch]

The ticket in the reference was closed. Thx for kicking the process forward.

Vít

Dne 22. 01. 24 v 18:33 Aoife Moloney napsal(a):
> Ok I have re-ran the script again, this time it finished so I believe 
> all F37 bugs are now closed <crosses fingers>. If you come across any 
> open ones, do let me know and I will re-run the autoclose script.
>
> Thanks!
> Aoife
>
> On Mon, Jan 15, 2024 at 8:22 PM Sandro  wrote:
> On 15-01-2024 09:52, Vít Ondruch wrote:
> > Any update? This ticket is still open:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2235331
>
> I believe the script is chugging along. I've seen a few more bugs
> being
> closed the last couple of days.
>
> -- Sandro
> --
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
>
>
> --
>
> Aoife Moloney
>
> Fedora Operations Architect
>
> Fedora Project
>
> Matrix: @amoloney:fedora.im http://fedora.im
>
> IRC: amoloney
>
> --
> _______________________________________________
> devel mailing list [e-mail]
> To unsubscribe send an email [e-mail]
> Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue

[Vít Ondruch]

Dne 08. 01. 24 v 13:00 Sandro napsal(a):
> On 05-12-2023 18:45, Tomas Hrcka wrote:
> > Fedora Linux 37 has gone end of life for updates and support on 
> > 2023-12-05.
> > No more updates of any kind, including security updates or security
> > announcements, will be available for Fedora Linux 37 after the said
> > date. All the updates of Fedora Linux 37 being pushed to stable will be
> > stopped as well.
>
> As part of the EOL tasks all bugs open for F37 receive an EOL notice, 
> first, and sometime later they will change status to CLOSED | EOL, 
> unless the version is changed.
>
> It seems the first step (notification) happened, but the second step 
> (closing) has not completed. IIRC, I saw some bugs being closed, but I 
> also see a lot of F37 bugs still open [1].
>
> Is that an oversight or did something go wrong during the procedure? I 
> cc'ed Aoife, who appears to have run the first step. I'm happy to open 
> a ticket if required.

There also used to be Rawhide bugs reassigned to latest stable Fedora, I 
might have missed something, but I don't think that has happened.

Vít

[Adam Williamson]

On Mon, 2024-01-08 at 18:10 +0100, Vít Ondruch wrote:
> Dne 08. 01. 24 v 13:00 Sandro napsal(a):
> > On 05-12-2023 18:45, Tomas Hrcka wrote:
> > > Fedora Linux 37 has gone end of life for updates and support on 
> > > 2023-12-05.
> > > No more updates of any kind, including security updates or security
> > > announcements, will be available for Fedora Linux 37 after the said
> > > date. All the updates of Fedora Linux 37 being pushed to stable will be
> > > stopped as well.
> >
> > As part of the EOL tasks all bugs open for F37 receive an EOL notice, 
> > first, and sometime later they will change status to CLOSED | EOL, 
> > unless the version is changed.
> >
> > It seems the first step (notification) happened, but the second step 
> > (closing) has not completed. IIRC, I saw some bugs being closed, but I 
> > also see a lot of F37 bugs still open [1].
> >
> > Is that an oversight or did something go wrong during the procedure? I 
> > cc'ed Aoife, who appears to have run the first step. I'm happy to open 
> > a ticket if required.
>
> There also used to be Rawhide bugs reassigned to latest stable Fedora, I 
> might have missed something, but I don't think that has happened.

I don't think that's quite right. What happens is that Rawhide bugs get
moved to the *new branched* (not stable) release, and naturally, this
happens at branch time, which hasn't happened for F40 yet.

https://docs.fedoraproject.org/en-US/program_management/pgm_guide/sop/branch...