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
