NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Mark Hahn, <hahn@neurocog.lrdc.pitt.edu>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Cool! (Score:1)
That sounds very intresting.
And pretty similar to what we're doing at work. But your handling of changes in different branches seems better. We basically use numbered migration levels and then sort out renumbering when merging to trunk.
That's a bit annoying when also dealing with maintenance branches.
Reply to This
Re: (Score:1)
We still need to do some renumbering when we merge to trunk.
We manage the problem (not solve, just manage) BASIC-style by incrementing the SQL version by 100 each release.
If someone it working on a branch, they'll having their own area of the 100...
migrate-2250-2251.sql
migrate-2251-2252.sql
(and so on for another 10 patches)
They may need to rename the first two numbers onto the final version for the release that they end up merged onto, but at least they don't need to do so while they are living on the branc