Berin Loritsch wrote:
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.
Berin:
What is the problem with doing both?
A couple of people have raised concerns about elinating the deprecated classes and methods. This can be addressed by doing a 1.1 release of LogKit (basically equivalent to CVS HEAD + update to Log4J version, and adding a 1.1 tag) following by an immediate cleanup of LogKit HEAD through removal of the deprecated content, tag the update as 2.0 and relase under 2.0.
CHeers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
