To sprint or not to sprint

Back home in Sweden, after a fairly uneventful trip and much faster than last time (one reason would be that this trip didn't include a stopover in San Francisco). Other than a long delayed connection flight in Philadelphia (isn't it just so much fun to hang around an airport for incremental values of "now delayed another 15 minutes"?), nothing bad. Interestingly enough, most of the delay was actually caught up before we arrived in Stockholm... I guess the wind-gods were on our side today.

Anyway. Post-conference code-sprint summary. I'll start by saying this was a brilliant idea - IMO it worked out really well. However, I'm not so sure I'd call it a codesprint. I had the vision of 30 guys tapping away like madmen on their keyboards trying to flood Bruce and Tom with as many patches as possible during two days, and that's not really what happened. Instead, there were plenty of time set aside for group discussions on separate topics (replications, dtrace etc), and the most important thing was the ability to talk to people before and around the coding. Tom, Bruce and other major coders were available all the time for questions and discussions about how to do things, which really helped. Writing the actual code can be done alone - especially with the good preparation you got here.

So. Maybe not a sprint, but still a very good "team-distance-running" or something. We've seen a few patches already come in, and I'd expect more over the next couple of weeks as people finish up the final parts when they get home.

For those interested, I spent most of the code time working on some of the final touches to the Visual C++ build system (thanks to David Fetter for helping me make my perl code actually look like proper perl), and also did some first stumbling steps on porting pg_regress to C. I definitly hope to have the VC++ stuff done in time for feature freeze, unfortunatly I'm not sure I'll have the time for pg_regress.