[Test-Announce] Fedora Linux 37 Final is NO-GO

[Ben Cotton]

Due to outstanding blocker bugs[1], F37 Final release candidate 3 was
declared NO-GO. Because of the upcoming OpenSSL critical vulnerability
disclosure, we are pushing the next target date out a week. See the
Fedora Magazine article[2] for more information.

The next Fedora Linux 37 Final Go/No-Go meeting[3] will be held at
1700 UTC on Thursday 10 November in #fedora-meeting. We will aim for
the "target date #3" milestone of 15 November. The release schedule[4]
has been updated accordingly.

Minutes[5] and full logs[6] are available on Meetbot.

[1] https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist
[2] https://fedoramagazine.org/fedora-linux-37-update/
[3] https://calendar.fedoraproject.org/meeting/10360/
[4] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
[5]
https://meetbot.fedoraproject.org/fedora-meeting/2022-10-27/f37-final-go_...
[6]
https://meetbot.fedoraproject.org/fedora-meeting/2022-10-27/f37-final-go_...

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
test-announce mailing list -- test-announce(a)lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org
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

[Michael J Gruber]

In this context, since we are still in freeze:

Can dnf distinguish between updates in testing and updates in testing submitted for
stable?

People might want to dist-upgrade to F37 now (I'm not critizing the release decision)
and want to get "the same updates as on F36". Ideally, no F36 package in stable
should be ahead of its F37 counterpart in stable, but due to the long freeze - or urgent
fixes - reality might be different.

It's fair enogh to say: If you want beta/RC I'll give you beta (with
updates-testing) ... and finally, if you turn off updates-testing at release time,
you'll end up with non-testing packages at some point in time after, of course.

[Neal Gompa]

On Fri, Oct 28, 2022 at 5:27 AM Michael J Gruber <mjg(a)fedoraproject.org&gt; wrote:
>  In this context, since we are still in freeze:
>
>  Can dnf distinguish between updates in testing and updates in testing submitted for
> stable?
>
>  People might want to dist-upgrade to F37 now (I'm not critizing the release decision)
> and want to get "the same updates as on F36". Ideally, no F36 package in stable
> should be ahead of its F37 counterpart in stable, but due to the long freeze - or urgent
> fixes - reality might be different.
>
>  It's fair enogh to say: If you want beta/RC I'll give you beta (with
> updates-testing) ... and finally, if you turn off updates-testing at release time,
> you'll end up with non-testing packages at some point in time after, of course.
No, there's no metadata for distinguishing that, since those queued
for stable are merely waiting for a compose run that allows them to go
through. Keep in mind, most updates in testing today will be queued
for stable in two weeks anyway.


-- 
真実はいつも一つ！/ Always, there's only one truth!