At 12:16 3/5/01 -0400, Berin Loritsch wrote: >COURSE OF ACTION >---------------- >Yes) We do the migration by Friday May 4 and release LogKit 2.0b1(?) >along > with Avalon Framework/Excalibur 4.0b1 > >No) We do NOT migrate LogKit for a LONG while (at least two full >release > cycles for Framework). In any event, LogKit (version number?) >should > be marked Beta1 along with Framework/Excalibur
Would you mind waiting to the 5th - then I could update Logkit the way I wanted to and that should remain stable. >REASONING >--------- >LogKit, Framework, and Excalibur are projects that are used directly by >developers. It is critical that the API be stable. There really hasn't >been much change to the LogKit API in a while--mostly just feature >enhancements and bug fixes. The critical API used in clients is the >Logger interface (which hasn't changed almost since the beginning) I don't think it has changed in any non-backwards incopmatible way at all ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
