Jan 30, 2012 at 5:00 PM
Edited Jan 30, 2012 at 5:10 PM
I now have a bit more complicated question.
The previous branching plan was to have one dev line and one MAIN. To maintain database changes, they were maintaining script changes by adding scripts to a folder and incrementing a number on each sql script and moving them from a dev line to MAIN. No pattern
followed by the guidance package here. So I've been working on a plan to convert them over to a Database Project and this was my plan.
We are ready to merge vNext into MAIN and it looks like it will not be too difficult. However prior to this I am wanting to make the transition from an the old way databases changes were happening. I want to implement a Database Project in that branch
and and merge it into MAIN. So now vNext will be referred to as vCurrent (after the physical merge has been done).
Now that the MAIN branch will have the new Database Project and the Release branches will have the database project, vNext and vNext+1 will also need to be converted. I am planning to merge the project (FI) to the two dev branches, update these databases
to vCurrent (which should not have any signifcant schema changes so it should be relatively easy). So now vCurrent will be throughout all branches.
For vNext and vNext+1 any scripts that have been put into these dev lines, I will run against a database that is vCurrent. After this is done I will update the Database Project off of the database that has vNext and vNext+1 changes in it.
This to me seems okay to get back on the Advance Branching plan. What do you think?