FreeBSD 15.0 is now "PRERELEASE"

[cperciva]

Chase URL change from the FreeBSD project.

Motivation and Context

As of August 8th (the start of the FreeBSD 15.0 "code slush"), FreeBSD 15.0 is now "PRERELEASE" instead of "CURRENT".

Description

URL has been changed. Further changes will be needed in 4 weeks when 15.0-PRERELEASE bifurcates into 15.0-ALPHA1 and 16.0-CURRENT.

How Has This Been Tested?

This has not been tested.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Quality assurance (non-breaking change which makes the code more robust against bugs)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

[behlendorf]

Thanks for the heads up. It looks like these images haven't yet been published, hopefully they'll show up in the next few days.

As as last week we've also started seeing reliable failures with the CURRENT image. These still need to be investigated, it'll be interesting to see if they're also present in the PRERELEASE image. Here's a recent example:

https://github.com/openzfs/zfs/actions/runs/16888203932/job/47841166561?pr=17616

[amotin]

@behlendorf This PR appeared after I reported the CI issue. The problem seems to be that kernel sources and ISO got out of sync due to last week ISO build failure, while the new sources were still published. Hopefully the mentioned PRERELEASE fix it all.

[cperciva]

Yeah I opened this because the email I got from @amotin and @markjdb reminded me that this change was going to affect you. Assuming nothing else breaks we should have working images this week, landing about 72 hours from now, at the updated URL -- no need to merge this now, I just wanted to open it pre-emptively.

[behlendorf]

Got it. Well, from my perspective we might as well go ahead and merge this now so we'll immediately pick up the new images once they're available. Unless you'd rather we hold off.

[cperciva]

I'm fine with this being merged now. The only reason to wait would be in case you want to test the change on Thursday before merging it.

[behlendorf]

Alright, once the CI wraps up I'll go ahead and get this merged.

[mcmilk]

Currently 15.0-CURRENT ist fine, but the PRERELEASE not. Why not leave it on CURRENT for now?

[cperciva]

Currently 15.0-CURRENT ist fine, but the PRERELEASE not. Why not leave it on CURRENT for now?

15.0-CURRENT wasn't in fact fine, because the latest VM snapshot we had was out of sync with the latest src tarball we had. The release cycle is being a bit bunpy but I'm hoping to get a VM snapshot out over the weekend.

[cperciva]

I finally managed to get a snapshot released. Can someone please confirm for me that 15.0-PRERELEASE is being picked up properly by the ZFS testing now?

[mcmilk]

I finally managed to get a snapshot released. Can someone please confirm for me that 15.0-PRERELEASE is being picked up properly by the ZFS testing now?

I updated another PR by me. We will see, how FreeBSD 15 runs there now....

Edit: some other problem now:

FreeBSD-kmods repository update completed. 199 packages processed.
All repositories are up to date.
Updating database digests format: . done
pkg: No packages available to install matching 'git' have been found in the repositories
pkg: No packages available to install matching 'qemu-guest-agent' have been found in the repositories

[cperciva]

I updated another PR by me. We will see, how FreeBSD 15 runs there now....

Looks like the VM image downloaded just fine, but the run failed because it couldn't install packages. This is to be expected; there's a package run in progress but it takes about a week to build everything. (And we threw out the previous package set because it was linking to old versions of libraries so none of the packages worked any more.)

So, things are still broken but they're moving in the right direction at least.

[behlendorf]

@cperciva how goes the package rebuilding?

[cperciva]

@cperciva how goes the package rebuilding?

Assuming you're talking about amd64: In progress, still a few days off for a complete package set. You can see the progress here: https://pkg-status.freebsd.org/beefy18/build.html?mastername=main-amd64-default&build=p9652f95ce8e4_sb45a181a74c