-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Use FreeBSD 15.0-RELEASE in CI #18013
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
base: master
Are you sure you want to change the base?
Conversation
And remove the obsolete FreeBSD 14.2-RELEASE. Sponsored by: ConnectWise Signed-off-by: Alan Somers <[email protected]>
| *) | ||
| # default list | ||
| os_selection='["almalinux8", "almalinux9", "almalinux10", "centos-stream9", "centos-stream10", "debian12", "debian13", "fedora42", "fedora43", "freebsd14-3r", "freebsd15-0s", "freebsd16-0c", "ubuntu22", "ubuntu24"]' | ||
| os_selection='["almalinux8", "almalinux9", "almalinux10", "centos-stream9", "centos-stream10", "debian12", "debian13", "fedora42", "fedora43", "freebsd14-3r", "freebsd15-0r", "freebsd16-0c", "ubuntu22", "ubuntu24"]' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be discussed, but from the perspective of testing oldest and newest versions, I think "freebsd14-3r" and "freebsd15-0s" pair by default made sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With (I think) absolute majority of FreeBSD users getting ZFS code from the base rather than from the ports/packages, testing of the new changes is much more relevant on a FreeBSD version where they will likely run, which is stable, when with time it become the next release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@asomers any thoughts on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alexander's reasoning makes sense. But I think we should still drop 14.2-RELEASE. I can't think of any reason to keep testing there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That part nobody objects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear, as I understand it the request was solely to change freebsd15-0r back to freebsd15-0s for the default case.
And remove the obsolete FreeBSD 14.2-RELEASE.
Sponsored by: ConnectWise
Signed-off-by: Alan Somers [email protected]
Motivation and Context
To do CI testing on the latest production release of FreeBSD
How Has This Been Tested?
CI change only; tested in CI
Types of changes
Checklist:
Signed-off-by.