A worthy cause, and we should all strive for it. It does put extra constraints on things like db upgrade scripts however. If ACS is releasable at all times, can users make their own release and expect all upgrade paths to work?
I disagreed with you on documentation as a commit criteria in another thread, David. I do favor (extensive) unit tests as criteria. Daan On Mon, Sep 16, 2013 at 6:05 PM, David Nalley <da...@gnsa.us> wrote: > On Mon, Sep 16, 2013 at 11:34 AM, Marcus Sorensen <shadow...@gmail.com> wrote: >> I think this discussion should be linked with the discussion about minimum >> requirements for a release (release criteria). It seems this discussion is >> already being had to some degree. > > > Agreed. I think release criteria are important - but really - release > criteria should be commit criteria (or at least commit to a > release/master branch) I think we get a better release by enforcing > better quality standards all of the time - essentially keeping > CloudStack 'releasable' at any point. > > --David
