Kris, Yes, I do think that including migration plugin fits well with Propel 1.3 plugin.
I also think we should include behaviors by default, but that is probably pushing it. Do you want to integrate and test? - Dustin On 7/11/08 12:04 PM, "Kris Wallsmith" <[EMAIL PROTECTED]> wrote: > > Dustin, > > Do you think incorporating a migration mechanism into the 1.3 plugin > makes sense? Something like sfPropelMigrationsLightPlugin? > > Kris > > On Jul 7, 10:46 am, Dustin Whittle <[EMAIL PROTECTED] > project.com> wrote: >> Kris, >> >> For 1.2 I am working in /plugins/sfPropelPlugin/trunk. I will create a list >> of issues to address and we can work from there. >> >> Cheers, >> >> Dustin >> >> On 7/7/08 9:22 AM, "Fabien Potencier" <[EMAIL PROTECTED]> >> wrote: >> >> >> >>> Kris Wallsmith wrote: >>>> Hi devs, >> >>>> I'd like to help with the development of 1.2, specifically the upgrade >>>> to Propel 1.3. Since this work will be done in the /plugins space, >>>> which I already have commit access to, I'm not sure what the protocol >>>> is here. Do I need the nod from Fabien to be able to help? From >>>> Dustin? >> >>> Dustin will coordinate this effort. >> >>> Fabien >> >>>> Thanks, >>>> Kris > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
