Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

packit: Add Fedora 39, drop Fedora 37 #407

Merged
merged 1 commit into from
Aug 23, 2023

Conversation

tomasmatus
Copy link
Member

No description provided.

@tomasmatus tomasmatus added the no-test For image rebuilds and manual test requests label Aug 23, 2023
Copy link
Member

@martinpitt martinpitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@martinpitt martinpitt merged commit f6fbb74 into cockpit-project:main Aug 23, 2023
3 checks passed
Comment on lines -44 to +45
- fedora-37
- fedora-38
- fedora-39

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if any of the existing aliases can't work for you so you don't need to update this twice a year... Sadly, I don't see any combination that would result in the same set of chroots. But maybe having fedora-all or fedora-development+fedora-latest-stable can work.

Maybe, we can create a new alias if really needed, but what is the rule here? Is it rawhide plus two branched ones?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our general stance is that we support the two most recent Fedora series, plus rawhide. I.e. once 39 branched off, we want to start releasing to that, and stop releasing to 37. But 37 will be in "stable" and "all" for a long time after that -- in previous releases, it even went on after EOL.

This is indeed a bit tricky to express -- fedora-latest would get us 39 now, right? and fedora-stable 38. But Once 39 gets released, they'd mean the same thing until 40 branches off from Rawhide. So we'd need something like "latest" and "latest-1".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-test For image rebuilds and manual test requests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants