2.1 has been too long in coming, but the wait is almost over. 2.1 is chock full of changes ranging from code reorganization and lots of new API to some cool new user features. We also tuned up our database queries a bit to improve speed and cachability. These tuneups required changing the database schema, which might break some plugins that do raw DB queries instead of using API. For this reason, we’ve been compiling a plugin compatibility list.
If you decide to try out the Release Candidate, please back up your database before upgrading. With a backup of your 2.0.x database you will be able to revert if RC1 does not work out for you. Once WordPress upgrades your database to 2.1, you cannot go back to your 2.0.x database unless you restore it from a backup. Caveat emptor.
As we’ve worked to bring 2.1 to a close, we’ve been thinking ahead to 2.2. With 2.2 in mind we solicited your ideas a week ago. We’d like to work some of the most popular feature requests into 2.2. Some great ideas have already been put forth, and I look forward to working on them.
2.2 will also mark a change in how we manage releases. We want to avoid doing another 2.1 that takes a year to release. 2.1 took too long because we got greedy with what we wanted to put in it. Changes kept creeping in. With 2.2 we’re going to start doing time based releases. We’re going to try to do a release every four months and limit the scope of the changes to what we can realistically achieve within that timeframe. The goal is to get cool new features into user’s hands more often instead of saving them up for the one big release every year. This also makes development seem more active to those who aren’t hanging out on the mailing lists and IRC channels.
While working on 2.2, we will continue to maintain 2.0.x and will begin 2.1.x maintenance. Expect to see 2.0 and 2.1 releases for years to come.
Get ready for 2.1. I hope you like it.