Carlos, > > Thank you very much for your fast answer. > > So basically I could download 1.1 stable from the repo and replace the > 1.1/lib/plugins/sfPropelPlugin with the one in your branch. Is it > enough? >
Yes, except in sfPropelLogger, you need to change ::ERROR to ::ERR (I use more verbose error constants, not the pear/propel constants). Otherwise, everything else should work (though I have not tested extensively). Please let me know if you find any issues along the way. Cheers, Dustin > Carlos > > On 22 mar, 23:56, Dustin Whittle <[EMAIL PROTECTED]> > wrote: >> Carlos, >> >> Do not use my branch for a production project. The code is stable and there >> are 8000+ passing tests, but there are undoucumented/unsupported nuances in >> my branch. You should use symfony 1.1 stable and the propel 1.3 plugin. When >> 1.1 is labeled stable, I will export propel 1.3 from my branch as a plugin. >> >> All of the useful tweaks that are in my branch, will get merged in to 1.1. >> If there is any functionality specifically you want merged, please let me >> know and we can discuss merging it into 1.1 stable. >> >> Cheers, >> >> Dustin >> >> On 3/22/08 9:07 AM, "Carlos Cuenca" <[EMAIL PROTECTED]> wrote: >> >> >> >>> 1) Do you have an estimation for the final release of sf1.1? >>> 2) As I will process quite amount of data, I was thinking on using >>> propel 1.3 I had been following dwhittle branch and commits and the >>> excelent work he is doing here. My question for this is how usable is >>> that branch, and if it could be ready for use on production. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
