Hulver wrote: > Some sort of plan for checking stuff into the STABLE tree would be good > as well. A checklist of things to check. A start would be > > 1. Add any extra vars/blocks/boxes in an update patch > 2. Add those same vars/blocks/boxes to scoop.sql > 3. Does the patch need documentation changes as well > 4. Any new modules are added to Bundle::Scoop & startup.pl > > Any more? I remember more than a couple bugs coming up because of the new database changes being in the patch but not scoop.sql, and vice versa. I don't think it would be that hard to write a script to diff the default scoop.sql and create a patch file for it, while skipping all new inserts to the comments, ratings, stories, etc tables. Automated things are good :) Now if only there was a language useful for scripting common tasks, and that could process text quickly and easily... ;-) Now that I think about it, with Apache::Test a sanity check could probably be written that would just make sure that Scoop could at least load into apache. That could make sure all the needed modules were in startup.pl and there were no syntax errors. -Andrew