Le 28/07/2011 16:02, Martin Sucha a écrit :
Hello,
On Thursday 28 July 2011 15:40:35 ryan weaver wrote:
Yep, totally agree with tagging, but using the 2.0.x naming wouldn't let
bundles communicate a BC-breaking release number properly (and I would like
to see transparency in the bundle docs about BC breaks, now that we're
stable). But, if we don't follow the 2.0.x naming, then we should at least
be consistent and verbose about the Sf2 version compatibility somehow.
I also think that bundles should have their own version number.
I have not used git much, but I think it should be possible to tag a revision
with multiple tags, so for example some MyBundle revision could have:
- v1.0.0 (indicating MyBundle 1.0.0)
- for-sf-2.0 (indicating compatibility with Symfony 2.0.x)
The tag for-sf-2.0 will probably need to be assigned to the latest bundle
version that supports sf 2.0.x as (I think) one tag cannot be assigned to
multiple revisions (please correct me if I'm wrong).
Regards,
Martin Sucha
But you don't know the latest commit that support 2.0.x until you break
the BC by stopping supporting it. And creating 2 tags in git would
represent 2 different releases.
--
Christophe | Stof
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
