Brian Aker wrote: > Hi! > > Once we push tonight this library will need to be installed locally in > order to compile Drizzle: > http://code.google.com/p/protobuf/downloads/list
My opinion is that this work should be done in a separate branch. We really need to solidify a better process by which we work in the main development line. Randomly adding requirements such as the above to trunk does not help to instill confidence in Drizzle. By contrast, having a branch which tests the use of proto buffers and clearly explains the additional lib requirements is a better option. We are getting to the point now where commits to trunk should not be done. Instead, commits should be to a separate branch and should be accompanied by: a) a working test case (this is dependent on petdance, rbradford, mschoon and gmaxia's work on the test suite) b) a fully (or mostly full) green grid display on the build farm for the *branch* of work which highlights the new code. Once green, then a merge to trunk should be proposed. Zero straight commits to trunk; only merges from a development branch. We make our lives harder by doing this hap-hazard and chaotic process of committing to trunk. Nothing wrong with chaotic pushes to development branches, but not to trunk... Just my 2 cents. Jay _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
