Maybe the better solution is to put the mailet API on a separate release schedule, so it's clear that James 2.1.x implements mailet API 1.0 and James 2.2 implements mailet API 1.1.
Absolutely, the sooner we get round to miving it into its own cvs module the happier I'll be. Though as a guy with no time I haven't much leverage at the moment!
Same here. :(
I think this is the first revision to the mailet API (aside from v3 changes) since its release many years ago. And as it's minor, I would move it to 1.1 as opposed to using the Microsoft versioning formula:
I thought we were on Mailet V2 already, is it really Mailet v1 James v2?
Maybe I just wanted an excuse to use my Microsoft joke. I don't think the mailet API has changed though... since we lost CVS pre 2001, I don't know if we can recreate. I'm happy with calling what we have mailet v2 if that's what people think it is.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
