On 27/05/2009, at 1:38 PM, Mike Bailey wrote: > > deploy:migrate has gone, it's in an extension you load in the > capfile now > When an existing user tries and fails to run deploy:migrate, what > will they see and how will they know what to do? > > How does leaving it in affect people deploying non-rails projects? > > I'm always reluctant to make a change that breaks existing > functionality without notifying the user of a workaround, usually > with a deprecation notice.
+1 Keith --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
