+1 for 3.2! And also, we should adopt that approach going forward (no more bug fix releases for the stable branch, except for the last release before 4.0 is out). That means updating the release TODO with e.g., not creating a branch for 3.2.x, only tag it. When 4.0 is out, we branch 3.x.y out of the last 3.x tag.
Shai On Saturday, May 14, 2011, Ryan McKinley <[email protected]> wrote: > On Fri, May 13, 2011 at 6:40 PM, Grant Ingersoll <[email protected]> wrote: >> It's been just over 1 month since the last release. We've all said we want >> to get to about a 3 month release cycle (if not more often). I think this >> means we should start shooting for a next release sometime in June. Which, >> in my mind, means we should start working on wrapping up issues now, IMO. >> >> Here's what's open for 3.2 against: >> Lucene: https://issues.apache.org/jira/browse/LUCENE/fixforversion/12316070 >> Solr: https://issues.apache.org/jira/browse/SOLR/fixforversion/12316172 >> >> Thoughts? >> > > +1 for 3.2 with a new feature freeze pretty soon > > --------------------------------------------------------------------- > 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]
