3 ms·

APIs are stable with-in major version numbers. Major releases allow for API/ABI alterations. * https://docs.freebsd.org/en/books/porters-handbook/versions/ htt

APIs are stable with-in major version numbers. Major releases allow for API/ABI alterations. * https://docs.freebsd.org/en/books/porters-handbook/versions/ https://docs.freebsd.org/en/books/porters-handbook/versions/

alberth 3y ago
Understood, but I'm not seeing what API/ABI breaking changes occurred hence why I ask. https://www.freebsd.org/releases/14.0R/relnotes/ https://www.freebsd.org/releases/14.0R/relnotes/ The "Runtime Libraries and API" section doesn't indicate any breaking changes, nor am I seeing it anywhere else in the release notes.
- LastTrain 3y ago
  Breaking changes are allowed, not required.
- throw0101b 3y ago
  * 004: 14.0-CURRENT after kernel interfaces for dispatching cryptographic operations were changed. * 008: 14.0-CURRENT after changing the internal KAPI between the krpc and NFS modules. * 010: 14.0-CURRENT after changing the sndstat(4) ioctls nvlist schema and definitions. * 022: 14.0-CURRENT after commit e1a907a25cfa changed the internal KAPI between the krpc and nfsserver modules. * 026: 14.0-CURRENT after changing the internal KAPI between the nfscommon and nfsd modules. * 037: 14.0-CURRENT after removal of thread argument from VOP_STAT(9) and fo_stat. * 043: 14.0-CURRENT after removing the unused thread argument from NDINIT(9). * 054: 14.0-CURRENT after changing irq_work_queue to return a bool in LinuxKPI to match 5.10 API. * 062: 14.0-CURRENT after struct kinfo_file changes. * 086: 14.0-CURRENT after vn_lock_pair() argument changes. See: * https://docs.freebsd.org/en/books/porters-handbook/versions/ https://docs.freebsd.org/en/books/porters-handbook/versions/ Kernel APIs are also part of the stability guarantee (unlike Linux).
- drewg123 3y ago
  One such changes is moving from OpenSSL 1.x to OpenSSL 3 in the base system, due to OpenSSL 1.x going EOL. That's one of the things that caused this release to take so long.

alberth 3y ago

Understood, but I'm not seeing what API/ABI breaking changes occurred hence why I ask. https://www.freebsd.org/releases/14.0R/relnotes/ https://www.freebsd.org/releases/14.0R/relnotes/ The "Runtime Libraries and API" section doesn't indicate any breaking changes, nor am I seeing it anywhere else in the release notes.

LastTrain 3y ago
Breaking changes are allowed, not required.
throw0101b 3y ago
* 004: 14.0-CURRENT after kernel interfaces for dispatching cryptographic operations were changed. * 008: 14.0-CURRENT after changing the internal KAPI between the krpc and NFS modules. * 010: 14.0-CURRENT after changing the sndstat(4) ioctls nvlist schema and definitions. * 022: 14.0-CURRENT after commit e1a907a25cfa changed the internal KAPI between the krpc and nfsserver modules. * 026: 14.0-CURRENT after changing the internal KAPI between the nfscommon and nfsd modules. * 037: 14.0-CURRENT after removal of thread argument from VOP_STAT(9) and fo_stat. * 043: 14.0-CURRENT after removing the unused thread argument from NDINIT(9). * 054: 14.0-CURRENT after changing irq_work_queue to return a bool in LinuxKPI to match 5.10 API. * 062: 14.0-CURRENT after struct kinfo_file changes. * 086: 14.0-CURRENT after vn_lock_pair() argument changes. See: * https://docs.freebsd.org/en/books/porters-handbook/versions/ https://docs.freebsd.org/en/books/porters-handbook/versions/ Kernel APIs are also part of the stability guarantee (unlike Linux).
drewg123 3y ago
One such changes is moving from OpenSSL 1.x to OpenSSL 3 in the base system, due to OpenSSL 1.x going EOL. That's one of the things that caused this release to take so long.