At some point it will become difficult if not impossible to support both branches of TMDA with one branch of TMDA-cgi. You might consider forking as I've done, or only supporting one of the two branches, etc. This in entirely up to you of course, I'm just being preemptive.
I'm not looking forward to supporting two separate branches, but I think that's what it'll come down to. Which is too bad, since I think we're still a ways away from a true "version 1" feature freeze, and it will be nice to include the new features which will soon be added to both branches. That will be a pain.
I will also need a new version numbering scheme that somehow still maps to the existing periodic table elements...
Maybe I'll keep using 0.X for releases which are compatible with TMDA-1.0, but start using 1.X for releases which are compatible with TMDA-1.1, doing 2 releases at a time.
Maybe I'll start doing that with release 14 "Silicon": There will be a 0.14 compatible with 1.0.x, and a 1.14 compatible with 1.1.x.
Unless anyone (Gre7g?) has a better idea, I think this is what will have to happen.
Another issue that might coincide with the above, is do you want a separate mailing list for tmda-cgi on tmda.net? I don't mind discussion going on in the main lists, but as tmda-cgi traffic gets heavy others might like to see it discussed in its own forum. One place for all things tmda-cgi might make even more sense if things get more complicated with multiple branches. Again though, this is up to you.
I think if the traffic gets worse it would be a good idea. As it is now, I think it's alright, as long as it's okay with you.
-- Jim Ramsay "Me fail English? That's unpossible!"
_________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
