In-flight issues for FreeBSD 14.1-RELEASE
We're experimenting with using this wiki page to help track issues leading up to FreeBSD 14.1-RELEASE. The hope is that it will work better and be more transparent than the previous "release engineering lead's inbox" method.
Issue identified
Issues start here.
Issue assigned
A developer is responsible for making sure this is fixed in time for the release.
* breakage on RPi 4 (karels)
Issue diagnosed
A developer is responsible for the issue and we think we know what is wrong.
* ldns issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278721 (des)
Patch being tested
A developer has a possible fix.
Patched in HEAD
A patch has gone into HEAD.
* one-true-awk import (imp)
Patched in STABLE
A patch has gone into the stable branch.
* disable NOMATCH events until devmatch has run (cperciva)
Merge approved
The release engineering team has approved merging the patch to the release branch.
Patched in release branch
A patch has gone into the release branch (or stable before the release branch is created).
Before BETA1:
* PHYS_IN_DMAP issue with non-contiguous layouts (andrew).
Before BETA2:
* REPRODUCIBLE_BUILDS was turned off for kernel (cperciva)
* llvmware update to 18.1.5 and remove obsolete sparc targets (dim)
* openzfs 2.2.24 (mm)
* Remnants of portsnap (olce)
* Problems with adduser/pw on 14.1-BETA1 (des)
Before BETA3:
* builds failing with pkg errors
- Due to pkg mirror configuration, not an issue in the src tree (clusteradm)
* i386 panics with drm-kmod (tijl)
* Accidental GDB_LOG (markj)
* OpenMP scheduling issues (dim)
* nfsd RFC8881 compliance (rmacklem)
* size of riscv binaries (dim/jrtc27/karels)
* Kernel handling of userland mutexes (olce)
* in6_addr field visibility (karels)
* non-UFS vm-images aren't being published (cperciva)
* vm-image cross-building should use qemu (cperciva)
* release build breakage with vm and cloudware both building qemu (cperciva)
Confirmed resolved
The issue has been confirmed to be resolved in the latest BETA/RC build.
Won't fix
The issue won't be fixed in the release (it's too late and not critical enough to delay the release).
* build reproducibility of ipmon and libarchive on amd64/i386 cross (dim, emaste)
- Too complicated to track down before the release; we'll build the i386 release in an i386 chroot.