Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The title this HN is post wrong, it should be "Evaluating FreeBSD CURRENT for Production Use" as used in the original article.

The capitalization is important, since it makes it very clear it's talking about the CURRENT branch.



Out of curiosity, as someone who doesn’t use FreeBSD what does “Current” (not all caps) imply instead?


It means the 'current' latest development code, not a release branch.

When FreeBSD cuts a release the code is handed over to a releng team (e.g on GitHub you'll see releng/13.1 atm) who handle security fix back ports and suchlike. Development then continues on master (or whatever the svn equiv is) until they cut another release.

So, this would be building from master. Or main. Whatever. Instead of using a release branch

:}


To clarify a bit: The release engineering team owns the branch during the release process, then hands it over to the security team.

(Of course there's always cooperation between the two teams -- the security officer has to get permission to commit to the release branch prior to the release but in practice that conversation consists of "we have a security advisory affecting the upcoming release" "go ahead". Theoretically the answer might come back "please wait a few hours because we're in the middle of builds right now" though.)


I'm not sure. The intent seemed clear without the capitalization. (Though I've been a FreeBSD user for over 25 years.)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: