-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Comments
The beta thing seems really really useful to ship/test new features and integration w/ the freshest stuff but wasnt that the purpose of |
I think by now 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. |
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 |
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 |
But I 100% ACK the new proposed bluefin stream layout |
GTS - Fedora -1 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. |
Ok to clarify what m2 means:
+1 to that! |
Also let's give this one a few days so we can get input from others. |
+1 for M2's proposal too! - The "beta" folder seems like such a good idea LOL i didnt even think about that |
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.The text was updated successfully, but these errors were encountered: