You should really only install -CURRENT if you're prepared to participate in fact-finding and troubleshooting sessions with the FreeBSD developers on the freebsd-current mailing list. The forums lack the knowledge and resources to answer in-depth questions about new developments and their ramifications.
Oh Thank you, I'm interested in working with current versions, so, I will email my problem to FreeBSD mail list.See 2.
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 questions on the forums run one of the officially supported versions (see the links at the end of this post), for which the installed user base is logically the broadest.
In terms of 'unsupported versions' we make the following distinction:
- FreeBSD versions that are...
- DutchDaemon
- Replies: 0
- Forum: Forum Rules and Guidelines (REQUIRED READING)
Thank you for your response but I'm interested in testing the future FreeBSD versions, Actually, I have no problem with the stable releases of FreeBSD (such as 14.2) and I just want to involve in the future FreeBSD versions more effectively.The problem is not so much that this forum doesn't support what you call "current" versions. The problem is that 15.0 is an experimental development version. It is intended for alpha testing by developers and volunteers. The name "current" doesn't imply that it is the newest supported and production-worthy version. On the contrary, it is not production worthy.
If you send a message to the mailing list "it doesn't boot", you are not doing anyone a favor. Matter-of-fact, you probably will not get a reply. On the mailing list, the expectation is that you would submit a detailed analysis of what is wrong, with dumps and traces, a root cause analysis, and perhaps a suggested patch.
My I suggest that you "work with current versions", which is 14.2 ?
Well, proper terminology isMy I suggest that you "work with current versions", which is 14.2 ?
-RELEASE
in this case. -CURRENT
is for the stuff that's still in development, like 15-CURRENT.If you're interested inThank you for your response but I'm interested in testing the future FreeBSD versions,
-CURRENT
, then the Forums are not the best place to bring up issues. As ralphbsz pointed out, participating in dev mailing lists is your best bet for getting some help, but expectations for participation are very different than on the Forums. It's really up to you to adjust your own expectations of what info you can get, and to learn what you need to bring to the table.Finally, I could install the FreeBSD CURRENT version in Virtual Box with no problem and I'm going to test anything in it. Is there any more priority testing list available that I can test through it one-by-one?Well, proper terminology is-RELEASE
in this case.-CURRENT
is for the stuff that's still in development, like 15-CURRENT.
If you're interested in-CURRENT
, then the Forums are not the best place to bring up issues. As ralphbsz pointed out, participating in dev mailing lists is your best bet for getting some help, but expectations for participation are very different than on the Forums. It's really up to you to adjust your own expectations of what info you can get, and to learn what you need to bring to the table.
It can be a lot of work to bring the required info to the table, but yeah, that's what it takes to be taken seriously there. I'd suggest browsing through the mailing list archives just to get an idea of how things work there, how issues are brought up, what's a no-no, stuff like that.
Just a heads up, mailing lists are NOT Discord or the Forums. You sometimes gotta have a thick skin, and to not expect to be taken seriously right away. But if you're ready to actually and stubbornly learn, go right ahead, bud.
Well, you can read what the Foundation writes about in its blogs, what is planned for the December release, and play with that. You can also look through the email archives to get an idea of what's being worked on. There are problems getting solved, bugs in Bugzilla getting referenced - active participation is expected. Just start with something that you think you can handle with your skill level. I'd suggest starting with fairly small and simple stuff that nonetheless needs to be resolved. It still goes through pretty standard steps, and culminates with a patch that you properly document (like where to apply it, which branch, what issue it solves) and submit.Finally, I could install the FreeBSD CURRENT version in Virtual Box with no problem and I'm going to test anything in it. Is there any more priority testing list available that I can test through it one-by-one?