Last year AREDN moved away from a formal set of beta test scripts and dedicated testers to a more agile beta general-release model.  Users were eager to get their hands on features they requested months earlier and help us test in preparation for a production release.   While we have been happy with the results, we have noticed that features that take a long time to develop only see the light of day months after development.  We have no easy way to learn from them before beta release.  Today, this is changing.
 
We are going to give anyone who wants it, access to the AREDN development branch builds, which includes the latest features we are developing… even before we are done with them!
 
We have been criticized by some for putting out too many releases.  Our philosophy, which does differ from some other organizations, is very much aligned to the vast majority of open source projects in the industry.  We are completely committed to following this successful model. It is an approach that is more suitable to our nature characterized by: dynamic requirements, a small number of developers, a culture that readily responds to change, and a user community of hams comprised of a highly technical subset who are mature enough to distinguish bleeding-edge from production-ready software.
 
AREDN uses a continuous integration build server (Jenkins)...