First off, congrats to everyone for getting Rails 2 released. A lot of work went into the release, and it's good to see us reach this milestone. And now that the release dust has settled, I think it might be useful for us to have a retrospective and evaluate how the release went.
I think the Ruby on Rails project has improved a lot this year, and this is another opportunity for us to learn what we can do to improve our release process for the future. In this latest release I saw some stuff that worked well, and a few things that were problems, and some stuff that could be improved pretty easily. I'm sure others have useful feedback too.
I've never done a retrospective online, but I'd guess some combination of email and campfire would be effective. Maybe set the stage via email, collect some initial feedback and distribute it, and then have a focused conversation in campfire once people are all prepared. That's just one idea for how to proceed, but I'd be happy with any approach that looked like it would be effective. I expect the core team has some good distributed discussion practices it's worked out that would work too. I think the point is to keep the discussion productive rather than either a lot of mutual back-slapping or a big bitchfest pile-on.
Thoughts? Anyone from core want to make this happen. I'm happy to work with folks to help out.