Not necessarily. If you want to know if your app works with upcoming FreeBSD release versions, you actually care - and you would know to check https://www.free

Not necessarily. If you want to know if your app works with upcoming FreeBSD release versions, you actually care - and you would know to check https://www.freebsd.org/releng/#freeze https://www.freebsd.org/releng/#freeze and https://www.freebsd.org/relnotes/CURRENT/relnotes/article.html https://www.freebsd.org/relnotes/CURRENT/relnotes/article.ht... and https://wiki.freebsd.org/WhatsNew/FreeBSD11 https://wiki.freebsd.org/WhatsNew/FreeBSD11 and be subscribed to the -CURRENT mailing list - which the development documentation indicate as mandatory when using a -CURRENT build. Then you would know whether the compiler suite is being torn out (remember? FreeBSD switched from GCC to LLVM/Clang - yes - that was done in the last -CURRENT development cycle) So your software might not even build because of certain base OS issues. BUT you would know all that already - and you would run -CURRENT in a VM that you blow away and rebuild as needed. Or in continuous integration like jenkins. https://wiki.freebsd.org/201405DevSummit/Jenkins https://wiki.freebsd.org/201405DevSummit/Jenkins BUT NO - you would use it in testing only. You wouldn't use it as a main platform. Unless you don't really care - then it's on you. Many devs run 10.1 and then run -CURRENT in VM's or on a spare laptop or machine for this purpose.