On Jan 18, 2014, at 10:45 PM, Peter Firmstone <j...@zeus.net.au> wrote:
> > > The major problem that faces my development now however is not multi threaded > bugs, instead it is the River development community remaining undecided on > supporting or not supporting Theory based development. > > You are mistaken in this statement, at least from my viewpoint. This idea of “Theory-based development” is a complete red herring. Speaking for myself, what concerns me is sweeping changes to code that has already been released. Especially when those changes are followed by a cascade of further failures, which then causes more sweeping, un-discussed changes. I want you to involve the community (including listening to us) in discussing the risks and benefits of making those changes, and developing a strategy to minimize the risks. Ultimately I think we need to extend our “review-then-commit” policy from API to the complete released codebase. Granted, qa_refactor is an experimental branch. So eventually the community needs to figure out how to move forward with experimental branches when they deviate significantly from the released branches. Cheers, Greg.
