To me, the feature set we have is fine for a 2.0 release. However, we need to be happy with the public API and be fairly confident in the quality.
I'm not strong on OSGi and people have mentioned problems with Eclipse. I would love to have someone with more OSGi experience provide guidance on what we need to do there. If you go through the Jira issues you will see some that relate to general features or qualities Log4j 2 should have. These are still open because they either have some feature that should be implemented or haven't clearly demonstrated the ability to meet the quality. Others are bugs or feature requests where no patch has been supplied. The others are bugs or features with patches. I try to apply valid patches as quickly as I can. The other stuff generally has fallen behind the requirements of my day job. I'm sure I could think of things for a 2.1 release but I am still focused on just getting 2.0 done. Ralph On Apr 10, 2013, at 3:50 AM, Remko Popma wrote: > Maybe it's too early to raise this, but I'm wondering, is there a todo list > for the new features/improvements that we'd like to get done before releasing > (the non-beta version of) Log4J 2.0? > > I know about JMX, but are there any other new features planned for the first > release? > > Are all outstanding Jira tickets in scope for 2.0? > Any Jira tickets or new features that could go in a 2.1 release? > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
