We have a third confirmation on the authentication bug which is pretty
serious now that we know it's not an isolated incident with Thunderbird.
This got me thinking a bit how dbmail could improve on the pre-release
testing.
Speaking for myself, I don't like to test cvs since there are just too
many changes in there to track to manage but would install the latest
release with real version number asap.
Perhaps dbmail could make it easier for admins to test pre-release stuff
by release RCXX packages often? one every week starting on feature
freeze date for that version even for 2.0.X minor stuff? This way,
non-devel users like myself could stress test while still having the
piece of mind of knowing exactly which bleed-version I'm running and
roll-forward or backward if errors are encountered, before the general
public get hold of it.
Right now for minor versions we have CVS, which I don't think have
enough people testing on, and immediate release.
New model for minor point releases:
CVS --> Feature Freeze --> 1-2 Week of RC testing (RC every 4 days or
whenever a large bug is found/fix, which ever is first) --> Release.
In this way, RC testing can begin right when feature freeze is announced
which.
Xing
