I have a few questions about the deploy task for 1.2 from you all. I would like to hear everyones opinion.
- How far are we trying to take the deploy task this round? I read somewhere the goal is to have something on the level of capistrano. - Do we want to integrate database migrations in to the programmable deploying interface? - Will it have the ability to integrate with source control for tagging, branching, etc. and generate patches to deploy code changes? This one really interests me because in the past I have used capistrano for managing svn tags, branches and deploying upgrades/ downgrades to code with svn diff and patch. I have always wanted to take it one step further and tie in database migrations to the process because currently I still run the processes a part from each other. Thoughts? - Jon -- Jonathan Wage http://www.jwage.com http://www.centresource.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
