Category Archives: release engineering

How to fix FreeBSD for corporations (and user with smaller installations), the tools-viewpoint

There is a huge discussion going on on hackers@ about how FreeBSD is not suitable for large installations (anymore?). As of this writing, the discussion seems to get some discussion-clusters. We have some sub-topics which could lead to some good improvements.

One subtopic is the release engineering. Some changes like a more guided approach of what should be merged to which branch, the frequency of releases and maybe some kind of long-term-branch(es). There is some discussion to get maybe some joined-funding in some way from interested parties to pay someone to take care about long-term-branch(es).

Another subtopic is the way bugs are handled in our old bugtracking software and how patches go unnoticed there.

And both of them are connected (parts more, parts less) by what can be done in a volunteer project.

To me it looks like the proposals “just

The return of the FreeBSD QA/release cycle graphs

I finally got around to updating these after having let them gather dust for a while. These include bar charts showing the time periods that various releases were being worked on (QA = Quality Assurance) and were supported by the FreeBSD security team. The dates for 6.4, 7.1, and beyond are all “best-guess”.

I find the graphs much easier to understand than the text-format descriptions in various emails.

The data are up at schedule.html.