msplsh I already told you there was a more explicit version in the past, telling how horribly broken Debian's packages are (and, again, they are indeed, I used them for a short time before dicovering that notice, and lots of stuff didn't work as it should, and no, that wasn't related to the version.). Still, this sentence that's still there should give you a clue:
Any issues or feature requests related to the packages from Debian provided distros will be closed with no feedback (or even rage feedback).
Noone in the world would ever give "rage feedback" if all it was about was some older version.
Large projects typically have release and support cycles. Trying to force them into the same cycle as your distribution creates tons of problems. This has been discussed for a long time in general, see e.g. 2004 posts
here and
here. Debian has a history of breaking stuff with their own patches, the most well-known incident being about OpenSSL in 2008 (actually introduced 2 years earlier IIRC). Patching software you don't know intimately is always somewhat dangerous.
The time is more predictable and has longer prep time when done with major releases, or even more predictable when versioned, versus ports that change these dependencies... whenever, maybe even real close to the end of the quarter.
FreeBSD ports keep software as close to upstream as possible, and changing a default version is typically done some time before the old version would be EOL, so the change makes it into the next quarterly branch (or, only in some exceptional cases when
other software needs features of the newer major release).
That's the only way to do it reliably, you'll find the same with every "rolling release" Linux dist. You
can have the quarterly snapshots, to reduce the frequency of possible work for the admin. In contrast to such a rolling release Linux dist, you still have your stable and supported base system with FreeBSD.
Just imagine people in the Windows world would expect their application software upgrade cycles tied to the OS (so, this could be MSSQL server, Sharepoint, IIS, .....). It would never work. Debian can
attempt to do something like that because the software distributed is open-source, but as said above, just patching away yourself is risky, especially when it concerns security fixes.