Hi Jeff,

 

You may be right about that (though I haven't seen it pulled down as a dependency for my Maven builds, yet...), but large organizations often don't see things the way you and I do.  They won't ditch an acceptable, stable log4j for what *appears* to be a beta.  After over 4 years of active development, though, it seems reasonable to expect multiple full releases of something as relatively small in scope as a logging framework.  The fact that we don't see a 1.0 yet perhaps indicates over-perfectionism.  This often happens with other OSS projects (JDOM being a notable case of this, as I remember).  For our sake, please just get to a reasonably stable build and label it "1.0".  We'll expect bug fixes and minor API changes, of course, as that's natural, and new features can be released incrementally.

 

Are there some must-have features that have yet to be implemented?  It would be nice if the FAQ were updated for this, along with a high-level road map.

 

Thanks for all for the hard work!
Ari