Personally I'd like to work on some new features. Specifically, binary logging, 
a memory-mapped file appender and providing configuration support for some 
system properties (async loggers, JMX). 

So I'd like to work towards a 2.1 release. 

As you said, if some critical bug pops up we can branch off the 2.0.1 tag, and 
do a fix on that branch. 

Sent from my iPhone

> On 2014/08/05, at 9:10, Matt Sicker <[email protected]> wrote:
> 
> Are there any outstanding issues we'd like to address in a 2.0.2 release, or 
> should we just start working toward 2.1 now instead? Because if we go the 2.1 
> route of focus, I've got a few branches to merge back together (thankfully, 
> git-svn will help a lot in that regard) into trunk.
> 
> As Ralph (IIRC) pointed out, we don't need to make an explicit 2.0 branch 
> since we can just branch from the 2.0.1 tag itself if necessary.
> 
> -- 
> Matt Sicker <[email protected]>

Reply via email to