A place to record potential blockers/errata for 14.0.
It is not critical, but having bug 246279 resolved before stable/14 gets branched will be nice. (See https://reviews.freebsd.org/D25155)
(In reply to Mark Johnston from comment #0) Hi Mark, It is not clear what is the latest date for submission of patches for 14.0 from https://www.freebsd.org/releases/14.0R/schedule/ We (AWS ENA) want to submit our fix to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270813 As suggested in https://reviews.freebsd.org/D39614 I would like to know how much time we have. Thanks, Arthur
(In reply to Arthur Kiyanovski from comment #2) Not a direct answer to your question, but some readers might be unaware of this announcement (1st of May): <https://lists.freebsd.org/archives/freebsd-hackers/2023-May/002208.html> >> Delay in 14.0-RELEASE cycle and blocking items
In our use case (academic research, scientific software development), the ability to run existing Linux binaries is pretty important. According to [1], there are many other use cases such as desktop usage. Bug 273662 covers a 3rd party Linux app crash that is a regression compared to 13.2-RELEASE. I do not know whether it is due to the changes in base or due to the broken port, but I would suggest to consider it as a blocker for 14.0-RELEASE. [1] https://wiki.freebsd.org/LinuxApps
Another change to bring in: https://github.com/libcxxrt/libcxxrt/pull/23