We've been doing pretty good recently at getting a new 3.1.x release out every month or so, congrats all around. :) I'd like to keep it up and get 3.1.6 released at the start of October, so just an fyi there.
However, I was thinking about this the other day ... Keeping the stable release updated is great and all, but what's going on with 3.2? We generally release a new minor version (3.x) every year or so, and it'll be 1 year from 3.1.0 in about 2 weeks. With the constant updates of 3.1, plus the addition of sa-update, we haven't felt a lot of heat to get 3.2 out, so we can do the "it's ready when it's ready" thing... But I think we need to generally figure out some kind of schedule goal that we want to hit. So just to throw it out there: how does end of December or the beginning of January sound for a 3.2 release? Is this achievable? I'd like to see us get tickets sorted out -- punt things from 3.2 that we won't get to, move things from "future" and "undefined" into 3.2 appropriately if they should get done first, etc. I'd also like to see us get the major changes between 3.1 and 3.2 documented appropriately -- API, config options, etc. Thoughts, comments, etc? -- Randomly Generated Tagline: A cat will blink when struck with a hammer.
pgpz8pxFTFaEc.pgp
Description: PGP signature
