Yeah we just start a different database if it going to be a huge amount of changes. There are probably many better ways of doing this I just have explored yet.
J.J. On 10/7/07, Aaron Rouse <[EMAIL PROTECTED]> wrote: > What do you do when client needs a fix on version 1.5 which has significant > database differences when compared to version 2.0 that you are currently > working on? We just maintain a separate copy of the DB for the versions for > cases like that but just curious on how others do it. > > On 10/7/07, J.J. Merrick <[EMAIL PROTECTED]> wrote: > > > > Rick, > > > > > > > > 3. Branch and tagging. "me: ::working on version 2.0:: client: I need > > to you fix something that is broken on the live server! me: ok:: > > switch to the trunk which is version 1.5, fix, deploy, switch back to > > v2.0 branch" no mess and no thought > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Download the latest ColdFusion 8 utilities including Report Builder, plug-ins for Eclipse and Dreamweaver updates. http;//www.adobe.com/cfusion/entitlement/index.cfm?e=labs%5adobecf8%5Fbeta Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:290501 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
