Comment 8 for bug 1521693

Revision history for this message
Bill Erickson (berick) wrote :

Some requests from the EG hackfest discussion:

1. Regular database reification. We want to create a fresh DB export to use as the first step in all new installs at regular intervals (e.g. w/ each major release) so that it's not necessary to install every upgrade script that precedes a given version -- clean up the cruft. This also helps with keeping the install files up to date w/ Postgres (e.g. avoiding deprecated operators).

2. Continue using version upgrade scripts / avoid Sqitch for production.

3. Given #2 above, remove revert scripts when Sqitch commits are merged to master. The idea here is that they should never be used in the mainline code once a change is committed. Faulty SQL changes are replaced with follow-up commits, not reverts. Reverts are still used for development.

4. Explore other Sqitch commands / options. Start with the 'rework' command as a potential for solving the problem of a single function being modified by multiple branches simultaneously.