Hi All, I can't think of much left to do on commons-logging. Perhaps it's time to start planning for a release?
I think we should wait for log4j to get a release out the door that supports the TRACE level. Despite debating this at great length, there still isn't a release out that implements this. Current state is: * current release is 1.2.9 * release #1.2.10 will not be used for various reasons * 1.2.11 is "imminent" and will not contain TRACE * 1.2.12 will follow "a few weeks" after 1.2.11 and will contain TRACE * 1.3 will follow soonish (and will presumably have TRACE too). After all this time, I think it's probably worth waiting a few weeks for 1.2.12 to be out. But I don't think it's worth waiting an indefinite amount of time for 1.3. What's the general feeling on this? === Apart from that, what's left to do? I've been through the diffs since the last release and updated the release notes. The doc still needs the layout tidied up, but all the info is there as far as I know. You may have seen that I've also updated the build to create commons-logging-adapters.jar containing just the classes in the impl package, ie not Log or LogFactory. This means it can safely be deployed in a webapp without danger of not being useable by code in a parent classloader due to duplicate Log class instances. And I've updated the build to put the version# in the jarfile name. We do need to decide what version# to use for the next release. I think 1.1 is a good choice. We also need to write up the new features in the user guide. Anything else? Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
