Software Releases
Full releases are roughly semi-annual
- SL96a, SL96b, SL97a
- Initial release does not cover full offline software base; STAF system material and infrastructure comes first, application codes follow
- Release break-in and debugging period is several months
Great collaboration desire for stability
- Must be balanced against need to develop the infrastructure and add capability to application code
Balance, once BNL based infrastructure team is in place, likely to lie at ~2-3 months between releases, with the team supporting a shorter break-in period, and serving greater functionality demands from a growing offline software developer community
- Single development path; no branching. New development builds on the latest release.
Release coordinator will be important member of that team
- Coordination and gradual automation of the release process
- Minimize the load of the release coordinator role, and participate in infrastructure development with remaining time