IMHO: It would be sufficient to re-work a little bit the scarily martial phrases in the respective guideline:
The FreeBSD Forums cater primarily to end-users and systems administrators. As such, the Forums focus almost exclusively on FreeBSD versions that are officially supported according to the official FreeBSD website. Since resources are scarce, the FreeBSD Forums strongly suggest that anyone asking...
forums.freebsd.org
Note also, that
"… strongly suggests …" does not exactly forbid somebody to post questions on non-supported versions, while
"All communication about -CURRENT should take place on the freebsd-current mailing list (join), not on the forums." can be seen as a prohibition. Perhaps we may argue, that a question alone makes not up for a comunication, at least one answer would be necessary for that.
Suggestions:
- Rephrase "… strongly suggest ..." to "… suggests …"
- Replace "All communication …" with "Communication about -CURRENT would preferably take place on the freebsd-current mailing list (join). Don't expect answers on the forums."
Even users not running CURRENT might want to learn about upcoming features and obstacles, and solely from this point of view, the strong prohibition could be relieved a little bit. The worst that may happen is, that questions may not become answered.
Users wanting to install FreeBSD on recent ARM-SBCs have quite often no choice other then to use CURRENT, because many things do not work in RELEASE branches. For example, I consider the support of the now 8 years old BeagleBone Black feature complete only with the upcoming FreeBSD 13.0-RELEASE, and this will be the first time that I deploy the RELEASE branch on my BBBs. The ARM mailing list is quite active, but for ARM users it might be good to get answers in a more comprehensive way.
I am not voting for a CURRENT forum, since allowing while still not suggesting discussions about CURRENT on all forums, would be a minimal invasive change, which would maintain the Forums structure, without the need of duplicating everything for CURRENT.