I've tagged 7 tickets as "critical" [1] for 1.1. All of them deal with CQL; I strongly believe that 1.1 needs to be where CQL goes from being "the future" to being "the present." We've been promising this for almost a year now and it's time to deliver.
All of these (with the exception of 3707, which is relatively quick) are in progress, and some (2475, 1391) are almost complete, but I don't think we're going to get all of them done by the 18th. Thus, I'd like to propopose postponing the freeze one more week, until the 25th. [1] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CASSANDRA+AND+fixVersion+%3D+%221.1%22+AND+resolution+%3D+Unresolved+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC On Mon, Dec 19, 2011 at 11:56 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > Just a reminder that for us to meet our four-month major release > schedule (i.e., 1.1 = Feb 18), we need to code freeze on Jan 18, which > is just about a month away on the calendar but significantly closer in > terms of man-hours as people take holiday vacations. > > I've taken a first stab at moving issues to 1.2 that were tagged 1.1 > but I'm pretty sure won't be done in time, with 34 issues remaining in > 1.1, which is fairly optimistic [1]. Please be aware of the timeline > if you are working on or reviewing one of these tickets, or if you are > planning to volunteer for one before the freeze. > > [1] > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CASSANDRA+AND+fixVersion+%3D+%221.1%22+AND+resolution+%3D+Unresolved+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC&mode=hide > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com