That’s correct - we haven’t been making release zip files for quite some time. I don’t recommend anyone use them.
I’d be happy to help you try and diagnose the problems you’re having with the master branch if you open an issue on the Boulder repo with the errors/problems you’re facing.
Like @Patches mentioned (thanks!) we announce our production updates on the status page. The basic workflow is that on every Tuesday* we merge the
master branch into the
staging branch and deploy
staging to the staging environment. On every Thursday* we merge the
staging branch to the
release branch and deploy
release to the production environment.
So whatever is in the
release branch should track the production environment.
* - We do occasionally skip releases when there are regressions or during holiday seasons. There wasn’t a deploy this week and there won’t be one next for instance.
Hope that helps! We’re certainly open to improvements to our release management process but it has been a low priority. That’s mainly because there are few external Boulder deployments that we know about. Hearing more about what you’re using Boulder for and how we can cut releases to better suit your needs might help adjust the priority