Keiron Liddle wrote: > That is one of the main problems with the old code, these components are > all linked together in bad ways, making it hard to improve and deal with > improvements to any particular part. > So work on the old code really means using the new code if these are to > be considered separate components.
I understand, and I will interpret these comments and other related ones together to be a veto on my proposal to try to merge the two branches. I totally understand and respect that, and will comply. I do think that I got the wrong impression somewhere along the way. To the extent that I am able to demand anything, I really think we must at the very least make it very clear in our web site/doc that the maintenance branch is not open for business except for bug fixes, and with perhaps a two-sentence explanation of why. That may prevent you from getting to have this discussion again. > I'm wondering how advanced it really needs to be before anyone wants to > work on it. It is almost suitable to be used with the docs that forrest > creates. I'll start in on it right away. If you have a specific task that a greenhorn can chew on, please let me know. Otherwise, I'm sure I'll be able to find something interesting. Victor Mote --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
