It's a common convention to give a Symfony plugin that is compatible
with Symfony version (let's say) 1.2 a version number that starts with
1.2, and then change the patchlevel number independently for each
bugfix release of that plugin (that is: fooPlugin 1.2.0, 1.2.1, and
1.2.2 are released as needed, not in lockstep with Symfony 1.2.0,
1.2.1 and 1.2.2).
When the plugin becomes compatible with Symfony 1.3, the version
number of the plugin generally bumps up to 1.3 as well.
However Symfony 1.3 and 1.4 threw a monkey wrench into the works:
plugins that work with Symfony 1.4 also work with Symfony 1.3. So to
reassure Symfony 1.3 users and get them to use your plugin, you might
make it fooPlugin version 1.3.0.
But it's also true that Symfony 1.3 tolerates stuff that Symfony 1.4
has removed. And you don't want to scare off Symfony 1.4 developers
who might assume your plugin isn't really 1.4-compliant. That argues
for calling it fooPlugin version 1.4.0.
So I'm looking at the best-known Symfony plugins, sfGuardPlugin and
sfDoctrineGuardPlugin, for some guidance here.
Both of those plugins currently have a 1.3 branch (and 1.3.x releases,
not synced to Symfony release minor version numbers). Both of those
plugins currently have a trunk where "new and interesting" stuff is
happening ("forgot my password" support and schema changes, at least
in the case of the Doctrine version).
I seem to recall that Jon Wage is planning to stabilize that new
stuff, then cut a 1.4 branch with those features (my apologies if I've
misremembered this).
So to my mind the implied version numbering convention for Symfony
1.3/1.4 compatible plugins is this:
* Version 1.3 is fully compatible with Symfony 1.3 and 1.4, but
doesn't really exploit them; it's the 1.2.x version, cleaned up but
not significantly different
* Version "1.4" is held in reserve as an opportunity to release some
more exciting, not trivially backwards compatible stuff as a new
stable release
* After that... well, you might have to break the convention and go
with 1.5 for a new and exciting stable release if you can't wait for
Symfony 2.0.
I'm aware that the Symfony plugins site helps out by showing users
what versions of Symfony a given version of a plugin claims to be
compatible with. So in principle we don't have to sync version numbers
with Symfony. But it seems to help users out.
So what I'd like to see in this thread is a little discussion of what
the best version numbering convention for plugins might be. We'll be
making an officially stable release of apostrophe shortly and we'd
like to communicate well by choosing a meaningful version number.
Thoughts?
--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.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.
