In-flight issues for FreeBSD 16.0-RELEASE
Issues being tracked leading up to FreeBSD 16.0-RELEASE. Please email re@ as soon as you become aware of an issue and familiarize yourself with the change request guidelines.
This page is primarily maintained by and for the release engineering team -- the *primary* purpose is to make sure that re@ doesn't forget about issues and knows whom to bug about them. As such there isn't much attention paid to providing helpful descriptions of issues here; it suffices that the person assigned to an issue will know what is being referred to. This page should almost certainly not be used as a source for public-facing descriptions of work landing in this FreeBSD release!
Issue identified
Issues start here.
- pkg should be part of the base system
- pkg should be built as a bootstrap tool so that it can be used to build packages
- _pkgbootstrap and package-pkg targets in Makefile.incl can go away
- got should be part of the base system
- got should be used everywhere git is currently used in src build and release logic
- -ALPHA should be treated as a flavour of release build rather than a flavour of snapshot, in both bsdinstall and Makefile.mirrors
- pkg needs to understand that packages for 16.0-STABLE (aka 16.0.snap) are newer than packages for 16.0.ALPHA* (aka 16.0.a*)
- possible integration of vmimage.subr with nanobsd and installation-image-creation into a more general "image.subr".
- database-creation tools (e.g pwd_mkdb) should optionally emit METALOG lines so they don't have to be added manually in Makefiles and image-building scripts
makefs should read all paths and canonicalize + sort them to avoid "files created before parent directory" issues, cf. https://reviews.freebsd.org/D53046
- installer for BETAs should offer choice of "install this BETA" or "install the most recent BETA or release".
- NO_ROOT and WITHOUT_QEMU should be collapsed to a single NO_ROOT option in src/release
- NO_ROOT should probably be default for release builds
- pkgbase package versions should not include timestamps, starting with BETA1 (?)
Issue assigned
A developer is responsible for making sure this is fixed in time for the release.
- pkgbase should be used to create installer images (ivy)
- mrsas should be used by default instead of mfi (phk / emaste)
Issue diagnosed
A developer is responsible for the issue and we think we know what is wrong.
Patch being tested
A developer has a possible fix.
Patched in HEAD
A patch has gone into HEAD but needs to be merged into the stable branch.
Patched in STABLE
A patch has gone into the stable branch but needs to be merged into the release branch.
This section should stay empty until releng/16.0 is created (BETA1); move items directly into the "patched in release branch" section below.
Patched in release branch
A patch has gone into the release branch (or stable before the release branch is created, or HEAD before the stable branch is created).
Won't fix
The issue won't be fixed in the release (it's too late and not critical enough to delay the release).