> the versionadded tag has a benefit: a bundle author reading the latest 
> doc will be aware that this feature is new in the latest release, 
> meaning that using it in their bundle requires dropping the support of 
> older Symfony versions. 
>
> That would be true if we don't already have changelogs to indicate what's 
have been added/removed/modified in a release.
Then I don't think it is strong enough argument to make the doc more 
confusing for new comers.
 

> However, I agree that the examples should use the preferred way in the 
> release they document. We should find another way to indicate that it 
> has been modified since the previous release and so requires some work 
> to support both. 
>
As stated above, it already exists: changelogs.
 

>
> -- 
> Christophe | Stof 
>
>

-- 
-- 
If you want to report a vulnerability issue on Symfony, please read the 
procedure on http://symfony.com/security

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


Reply via email to