Completely agree withe the criticism, I should have been more thoghtful, with that in mind, I'll revert all the BC breaking changes on master, and merge in the release-2.5.6 branch that should contain just the bugfixes. There is another branch called release-2.6.0 which will contain the code that will hinder, but not break backwards compatibility. It is important to remember that the backward compatibility code is all documented in the capfile, and can simply be loaded back in, restoring old functionality.
I look forward to any more feedback, positive or negative or otherwise: - http://github.com/capistrano/capistrano/ ( head represents 2.5.6 ) - http://github.com/capistrano/capistrano/tree/release-2.5.6 - http://github.com/capistrano/capistrano/tree/release-2.6.0 - Lee 2009/5/27 Keith Pitty <[email protected]> > > 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 -~----------~----~----~----~------~----~------~--~---
