On 20 Sep., 21:05, Fabien POTENCIER <[EMAIL PROTECTED]> wrote: > To sum up, the new system reads the symfony dependency versions in the > package.xml and acts accordingly. > > So, you can create a new branch for the sfDoctrinePlugin repository and > still be able to maintain the old branch if needed. To ease things, you > can also change the major version of the plugin. Version 1.XXX for the > sfDoctrinePlugin that works with symfony 1.0 and 2.XXX for the one > working with symfony 1.1.
Maybe we use version 1.1 for the branch ;-) Where should we create such a branch for sfDoctrinePlugin? I suggest to move sfDoctrinePlugin in subversion to sfDoctrinePlugin/1.0 or so and add a new subdirectory: sfDoctrinePlugin/trunk or what do you think? I mean I guess this is not the only plugin that will have that "problem". > I'm also working on a trac macro to output a table with all available > versions of a plugin with dependencies and symfony versions. It is also required to have separate wiki pages for different branches. For the symfony 1.0 and 1.1 compatible branches there will be some significant differences, like the new CLI and the event system. Regards, Matthias --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
