Hey all,

I know Ian(pookey) had brought up the naming convention we are to use for
plugins branches and tags and I think using symfony-x.x.x can be misleading.
In another thread Fabien mentioned we should use the exact same naming
pattern that symfony uses, and I think we should do that.

A plugin branch should almost always relate to the same branch name in the
symfony svn. Here are some examples:

sfDoctrinePlugin/branches/0.1 - This is a special case. Requires
symfony 1.0branch but is named
0.1 because it was the first version of sfDoctrinePlugin to work on symfony
1.0

sfDoctrinePlugin/branches/1.0 - This is the latest symfony
1.0sfDoctrinePlugin and requires the symfony
1.0 branch

sfDoctrinePlugin/trunk(sfDoctrinePlugin/branches/1.1) - This is the latest
development of sfDoctrinePlugin and trunk will almost always require the
latest development version of symfony. When a plugin becomes stable and
launches it should be branched to branches. When symfony 1.2 or
symfony 2.0comes out, the branches/1.1 will be created so that we can
continue
developing in trunk to make the plugin work with the latest version of
symfony

sfGuardDoctrinePlugin/branches/0.1 - This is the same special case as above.
This version of the plugin requires 1.0 but it was the first beta version
and it requires sfDoctrinePlugin/branches/0.1

sfGuardDoctrinePlugin/branches/1.0 - Works with symfony 1.0 and requires
sfDoctrinePlugin 1.0 branch

sfGuardDoctrinePlugin/trunk(sfGuardDoctrinePlugin/branches/1.1) - Works with
symfony 1.1 and requires sfDoctrinePlugin 1.1 branch.

Now tags should be used for point releases of a branch, but are not totally
necessary. The pattern would be as follows.

sfDoctrinePlugin/tags/RELEASE_0_1_0, RELEASE_0_1_1, etc.
sfDoctrinePlugin/tags/RELEASE_1_0_0, RELEASE_1_0_1, etc.
sfDoctrinePlugin/tags/RELEASE_1_1_0, RELEASE_1_1_1, etc.

-- 
Jonathan Wage
http://www.jwage.com
http://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
-~----------~----~----~----~------~----~------~--~---

Reply via email to