Server software release management

There is no formal release system for the BOINC server software. This is because we have no way of thoroughly testing the software. Many of the features are project-specific and would take elaborate setup to exercise. If anyone wants to work on this, let me know.

Instead, we try to ensure that master is always production quality. When you develop a new server feature:

  • Do it in a branch
  • Test it thoroughly, preferably on a production project like SETI@home.
  • Tell boinc_dev about it, get feedback, resolve any issues
  • Only then merge it into master.
Last modified 5 years ago Last modified on Dec 12, 2016, 4:09:45 PM