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

Define bluefin release stream structure #1941

Open
castrojo opened this issue Nov 18, 2024 · 9 comments
Open

Define bluefin release stream structure #1941

castrojo opened this issue Nov 18, 2024 · 9 comments
Labels
enhancement New feature or request

Comments

@castrojo
Copy link
Member

We should start talking about this. Leaving out stable-daily it's:

gts: Fedora 40
stable: CoreOS Stable
beta: CoreOS Testing
latest: Fedora 41

How about:

gts: Fedora 40
stable: CoreOS Stable
testing: CoreOS Testing
latest: Fedora 41
beta: whatever, probably fedora's next release, undefined and YOLO if you opt in

I don't think we need to bring CoreOS next over. But, I'd also like to talk about making testing be where we land Bluefin changes that need a shakedown. Then we can maybe do a thing where we can use a bot or something to selectively merge features from testing to gts/stable. Don't make me use the git cli pls lol.

@castrojo castrojo added the enhancement New feature or request label Nov 18, 2024
@dosubot dosubot bot added the dx Developer Experience Image specific label Nov 18, 2024
@castrojo castrojo removed the dx Developer Experience Image specific label Nov 18, 2024
@tulilirockz
Copy link
Collaborator

tulilirockz commented Nov 18, 2024

The beta thing seems really really useful to ship/test new features and integration w/ the freshest stuff but wasnt that the purpose of :latest? - Dont the main images not have rawhide or something? Idk if we could even do that

@castrojo
Copy link
Member Author

I think by now latest just should be vanilla current version of Fedora. There will be people who want that but don't want to be beta testers of bluefin features. And if you see testing you know you're going to be a guinea pig, where as latest doesn't explain that.

As for the rawhide thing that's never been tenable for us for practical reasons, that's the distro's test channel anyway, not ours. We're kind of only interested in the final thing they publish.

@tulilirockz
Copy link
Collaborator

tulilirockz commented Nov 18, 2024

Sounds pretty nice! Testing seems like a really nice name for that! - I also propose we should try using separate branches for each stream, kinda like nixpkgs does. It would be a stream like testing -> latest -> stable -> gts or something like that, that would allow us to have stream-specific fixes for temporary things, and would make it so recently merged changes dont affect the other branches straight away (then we dont need to wait till the :stable/:gts tags are built until we can merge a PR). I'm 99.9% sure there are github bots that do that kind of work for us too

@tulilirockz
Copy link
Collaborator

Thinking about it, this probably should be a separate issue if you guys think this is a good idea we can try to go through

@tulilirockz
Copy link
Collaborator

But I 100% ACK the new proposed bluefin stream layout

@m2Giles
Copy link
Member

m2Giles commented Nov 18, 2024

GTS - Fedora -1 w/ gated kernel + zfs
Stable - CoreOS version w/ gated kernel + zfs

Latest - Fedora Current, current kernel, no zfs. Since we have a latest tag, this I think is the least surprise and is the closest to upstream Fedora. While you will experience bugs, this is most of the time due to Fedora current version. If anything this could be where coreos-testing exists if we want to make that a more permanent thing.

Beta - this is for testing. While right now it's being used as a smoke test by following coreOS testing, it really should be thought of our one tag that is for playing around.

We are already offering a lot of dials between GTS, stable, stable-daily, and latest.

Like having beta on coreOS testing around the bump for stable was nice to be able to test it out. Before latest bumped again being able to preview and see that ISO builds would be broken was nice. Beta to me is that playground tool.

@castrojo
Copy link
Member Author

castrojo commented Nov 18, 2024

Ok to clarify what m2 means:

gts -> stable -> latest

beta: whatever is incoming, either via bluefin or if we're enabling the next release branch. m2 says: Add a directory called Beta under system_files and boom it's separated out.

+1 to that!

@castrojo
Copy link
Member Author

Also let's give this one a few days so we can get input from others.

@tulilirockz
Copy link
Collaborator

tulilirockz commented Nov 18, 2024

+1 for M2's proposal too! - The "beta" folder seems like such a good idea LOL i didnt even think about that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants