| Warning |
|---|
Draft for discussion |
Rationale
Sakai has historically followed a strategy of 'code freeze' in anticipation of a release, whereby the entire trunk is branched at a particular snapshot in time, and from that point forward only verified bugfixes are merged into the branch. This has been an effective tactic in allowing development work to continue while still closely guarding the stability of the code being tested for release. It has also had the benefit of simplicity: a single deadline for everyone to get their work done in time.
...
Independent releases of individual components, coupled to clear expectations about what these component releases should include, could begin to address these concerns. If general release QA could begin by bundling together tested and documented component versions, this should provide firmer footing for the release process than a single, global code freeze.
Expectations on Component Releases
...