On Fri, Oct 28, 2022 at 5:27 AM Michael J Gruber 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
>
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
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
Due to outstanding blocker bugs[1], F37 Final release candidate 2 was
declared NO-GO.
The next Fedora Linux 37 Final Go/No-Go meeting[2] will be held at
1700 UTC on Thursday 27 October in #fedora-meeting. We will aim for
the "target date #2" milestone of 1 November. The release schedule[3]
has
Due to outstanding blocker bugs[1], we do not have a current release
candidate. As a result, Fedora Linux 37 Final is NO-GO.
The next Fedora Linux 37 Final Go/No-Go meeting[2] will be held at
1700 UTC on Thursday 20 October in #fedora-meeting. We will aim for
the "target date #1" milestone of 25
The Fedora Linux 37 Final Go/No-Go[1] meeting is scheduled for
Thursday 13 October at 1700 UTC in #fedora-meeting. At this time, we
will determine the status of the F37 Final for the 18 October early
target date[2]. For more information about the Go/No-Go meeting, see
the wiki[3].
Currently, we
