When there are dependencies with the SF version, i work with plugin/ branches/1.0 & plugin/branches/1.1 This does not allow versionning of the plugin, but an old version of a plugin should be a tag rather than a branch, no ? For simple plugins, this is enough, but yes we lack the full standard structure of SVN.
I find the pattern "PLUGIN_VERSION-SF_VERSION" a bit too heavy. Whereas the "subfolders" rule should answer to all needs, without being too unreadable. I vote for this one. Latest little point, absolutely not mandatory : in the projects I manage in my company, I always create a "latest" tag, which is updated each time a new tag is created. If there is a strong versionning rule, and many versions, we even have "latest-1.x", "latest-2.x", etc... If you maintain a plugin with many versions, this kind of shortcut can be very useful for your users, think about it ;) (especially if you have a neat versionning politic in which you ensure x.y.z will always be compatible with x.y.w). On 5 mai, 10:53, "Jonathan Wage" <[EMAIL PROTECTED]> wrote: > The problem with that scheme is that it does not easily allow organization > for multiple versions of the plugin, available for multiple versions of > symfony. We can either have the plugins organized in to subfolders or have a > naming scheme for the branches and tags. > > Subfolders(Pattern: plugins/sfPluginName/SF_VERSION/branches/PLUGIN_VERSION > --------------- > plugins/sfDoctrinePlugin/1.0/branches/1.0 > plugins/sfDoctrinePlugin/1.0/branches/2.0 > plugins/sfDoctrinePlugin/1.1/branches/1.0 > plugins/sfDoctrinePlugin/1.1/branches/2.0 > > Naming Scheme(Pattern: > plugins/sfPluginName/branches/PLUGIN_VERSION-SF_VERSION > --------------- > plugins/sfDoctrinePlugin/branches/1.0-sf1.0 > plugins/sfDoctrinePlugin/branches/2.0-sf1.0 > plugins/sfDoctrinePlugin/branches/1.0-sf1.1 > plugins/sfDoctrinePlugin/branches/2.0-sf1.1 > > In the above examples we have sfDoctrinePlugin 1.0 for symfony 1.0 and 1.1. > We also have sfDoctrinePlugin 2.0 available for symfony 1.0 and 1.1. > > I vote for subfolders. > > - Jon > > On Mon, May 5, 2008 at 3:31 AM, Nicolas Perriault <[EMAIL PROTECTED]> > wrote: > > > > > > > > > On Mon, May 5, 2008 at 10:06 AM, markus.staab <[EMAIL PROTECTED]> > > wrote: > > > > easiest way would be to have the same structure for plugins as in the > > > symfony core.. > > > > so > > > branches/1.0 > > > branches/1.1 > > > +1 for this scheme > > > ++ > > > -- > > Nicolas Perriault > >http://prendreuncafe.com/blog > > GSM: 06.60.92.08.67 > > -- > Jonathan Wagehttp://www.jwage.comhttp://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 -~----------~----~----~----~------~----~------~--~---
