On Mon, Jan 24, 2011 at 4:07 AM, Shai Erera <[email protected]> wrote: > This will allow us to release 3x as frequent as we want, hold on w/ trunk as > much as we want, and at some point cut over to 4.0 and think about the next > big things we'd like to bring to Lucene. >
+1, this way development is simple: we are always working on the next big release in trunk (for incompatible changes), and port compatible changes back to the next minor release. this seems to be working now, so lets stick with what works. when we release 4.0, 3.x goes into bugfix-mode like 2.9 is now, we start working on 5.0 in trunk, and open up branch_4x to backport compatible changes (e.g. for 4.1) also, I think its simpler to users: no confusion such as 4.1 not being able to read 3.4 indexes or similar silliness: to the users the versions are still completely sequential. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
