Peter, The decision to stop work in trunk--and to place all efforts into alt-design, should be put to a vote first by the committers. I'm quite reluctant for us to be putting all our eggs in one basket at this time.
I want alt-design to "win" because it became the better implementation over an optimized trunk code--not because we kept purposefully trunk incomplete, buggy and unoptimized so that six months down the road we had no other choice but to go to alt-design. And if we kept trunk unimproved, what would happen should the "lead developer" on alt-design find out he doesn't have the time to complete his work? We've been in this situation before--this is a very time-consuming project and it could happen. We need a fallback. What *does* work is continually modularizing the code so alt-design can better fit in component-by-component where possible, and also incorporating your findings within the trunk design so we can continually reduce the delta between the two branches. (Besides...some of us happen to enjoy "hacking code" and optimizing it...Don't take away our fun! ;) Glen --- "Peter B. West" <[EMAIL PROTECTED]> wrote: > Victor Mote wrote: > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
