How the FreeBSD Project’s Processes Help Companies Build Products
Posted by admin on Jan 5, 2010
George Neville-Neil has written the lead article for the January issue of the Open Source Business Resource (OSBR) and the FreeBSD Foundation is the sponsor for this month’s issue. The entire issue is available as a PDF and George’s article is also available in HTML.
From the article’s abstract:
The processes that open source projects use to produce new work and maintain the quality of their code base is a subject that comes up infrequently in discussions of open source. One reason for this is that engineers and programmers are usually loathe to deal with issues that are not directly related to the piece of code or technology that they are working on.
FreeBSD Project receives Bad Code Offset
Posted by admin on Jan 5, 2010
The Bad Code Offsets project of The Alliance for Code Excellence is
“a way to undo the bad code other people have written without actually replacing the bad code. Much like carbon offsets, money used to buy Bad Code Offsets goes towards open-source projects which not only produce good code, but produce software that helps developers build good software”.
The FreeBSD Project was recently added as a supported project and the FreeBSD Foundation will be receiving a check for $500. Thanks to those who suggested the FreeBSD project be added and to the Alliance for supporting good code!
Source: FreeBSD Foundation Blog
FreeBSD 8.0 Beta1 Released
Posted by admin on Jul 7, 2009
The first public test build of the FreeBSD 8.0-RELEASE test cycle is now available, 8.0-BETA1. Through the next week or so more information about the release will be posted but here is the current target schedule for the other ‘major events’:
- BETA2: July 13, 2009
- BETA3: July 20, 2009
- RC1: July 27, 2009
- RC2: August 17, 2009
- RELEASE:August 31, 2009
People with the resources to do so (test machines…) are encouraged to give 8.0-BETA1 a try. At this point it is not quite ready for production systems but mostly because there is still some ongoing work in a few areas that may cause some changes in things like ABI/API. Debugging support (WITNESS, malloc debugging, etc.) are also still turned on and those tend to cause a performance hit. As far as we know there are no known issues that would cause data corruption or anything like that, just the issues with performance and potential for changes caused by ongoing work. If you find problems they can be reported through the normal Gnats based PR system or posted to the mailing lists.
More details van MD5 checksums can be found on the release statement