Peter J. Holzer wrote:
Here are the patches I made for 0.29 while preparing my RPM and .deb files, and which still apply cleanly to the trunk (revision 458), so I guess I would like to see them in 0.30, when it is released.
I'll check these patches and apply them to trunk, but unless Ask agrees otherwise, IMO these are too late to go into 0.30 (but perhaps we can get 0.31 out RSN). Bringing up the subject of cutting a release should not normally be viewed as a call for patches; even on as relatively loosely managed project like this, the whole point of making releases is to capture a measure of stability before moving forward again.
Now that Ask has made a tag for a Release Candidate, we shouldn't really apply any patches which aren't bugfixes, since there wouldn't be any burn-in time with any new features (I've been running [more or less] trunk on several production boxes for two weeks). I'm more than happy to be outvoted on this, though. Most of the patches you submitted are hardly controversial (other than SIGCHLD), so if Ask, et al, are happy enough to add features and cut an RC3, I'll get them in. I just needed to bring this up as not best practice.
John
