On Monday, January 7, 2013 4:53:35 PM UTC+1, Lukas Kahwe Smith wrote: > > > On Jan 7, 2013, at 16:51 , Victor Berchet <[email protected] <javascript:>> > wrote: > > > > > 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. > > > > well .. just because something is documented somewhere doesnt make it > easily accessable. if i am working on adding a feature i will look in the > docs and not in the changelog. so i might not be aware that the feature i > am looking to start using is actually only available for the current > version and not a previous version i might also support. > > regards, > Lukas > > The Symfony docs (I mean book here) do only document (parts of) the user facing API & options - that is probably not the place you should look at when working on a new feature.
There is also an API doc that is exhaustive and could be used to know when something has been introduced. To sum up: A clean & readable book for users - each release has its own version. The changelog, upgrade files and the API docs for developpers. Cheers, Victor -- -- 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 [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
