Couldn't you create tags/trunk/braunches under /plugins/sfDoctrine/
On 9/20/07, Matthias N. <[EMAIL PROTECTED]> wrote: > > > On 20 Sep., 18:07, Kiril Angov <[EMAIL PROTECTED]> wrote: > > Matthias N. wrote: > > > Hi, > > > > > we, Jon Wage and I discussed today to create a new Doctrine plugin > > > that will be symfony 1.1 only with support for the brand new features > > > of Doctrine and symfony as well. > > > > > I just wondered if it is possible to have the name "sfDoctrinePlugin2" > > > as it is the second version of the plugin - not of Doctrine!? IMHO > > > "sfDoctrine2Plugin" would not reflect what it actually is. > > > > > I want to create a wiki page for a bit of brainstorming before we > > > start implementing it. > > > > > Is it possible to have the "2" at the end for the wiki page as well as > > > the plugin name? Or does this not work with the installer or the magic > > > on the website? > > > > > Regards, > > > Matthias > > > > Very good point not just for that plugin. I was thinking what will > > happen with the plugins installer when symfony 1.1 is out and most of > > the plugins are not compatible so one could usehttp://plugins.symfony- > project.com/sfHamlViewPlugin-1.0.0instead ofhttp://plugins.symfony- > project.com/sfHamlViewPluginin order to force a > > certain version but better will be if the symfony plugin installer knows > > which version of the plugin is compatible with the running symfony > > version. So if my project is 1.0.x then the install command will > > download the highest version of the plugin which is compatible with > > 1.0.x and if the project is 1.1 will simply get the latest version > > (which always will mean it is compatible with 1.1). Also for some > > plugins will be easy to have one version which is both 1.0.x and 1.1 > > compatible but for others not that easy (just to raise the issue) > > > > So to give my input on the original question. I would suggest you keep > > the same name but just specify in the pear package.xml which version for > > symfony it is. Putting numbers to the plugin name is kind of redundant, > no? > > yeah.. just wanted to know how to handle this.. > Keeping the name is a possibility - but then we need a way to have > both branches in subversion. > I hope to here something from official source. > > Regards, > Matthias > > > > > > -- Dave Dash 612.670.0621 Discover your favorite restaurant: reviewsby.us gtalk: dave.dash --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
