We need to focus on the task at hand. That is specifically, the
release of LogKit. Throwing in Deprecation policies into the mix
and other stuff as well is not helping.
#1) We focus on LogKit and answering the problems associated with
its release.
#2) We do a quick lessons learned, and if we need to adjust anything
else, we do it.
As to point #1:
Do we release LogKit 2.0, which essentially removes *all* deprecated
classes and methods? Or do we release LogKit 1.1 which adds all the
LF5 classes and leave the deprecated ones alone.
If we go for LogKit 2.0 I can commit what I have which removes all
deprecated classes.
We will *wait* on converting to Maven until after they release the
next version. That means we do not do any changes to the build system
at this time.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
