I think it would make a lot more sense if the documentation is stored in the repo of the components themselves. This way, you would get specific documentation to that particular version/branch.
Drak On 8 February 2012 21:51, Jamie Learmonth <jrlearmo...@gmail.com> wrote: > Hi devs, > > The release cycles of the Symfony Components seem to be creating some > confusion at the moment. The main problem lies in the documentation and the > versions currently available on pear.symfony.com and composer which do > not appear to be in sync. Basically, users read about cool stuff in the > documentation (such as ->setCode() on Console component and > useIncludePath() on ClassLoader to name a few), hop onto pear/composer to > try it out but of course it doesn't work. Then to increase confusion and to > pick on the Console component again, when browsing the 2.0 symfony branch > the README.md of this component also documents this feature when it is not > yet available in that branch. > > This confusion is happening because the documentation for the symfony > components on the symfony.com website is linked to master rather than the > stable 2.0 branch so it is not relevant to the code a majority of users are > using. When you bump symfony to 2.1 this will probably all sort itself out, > but 2.0 users will still fall foul because the documentation on the site is > not versioned (yet). Whilst I have your attention, it would also be nice if > the components were as decoupled from symfony releases as they are from > symfony so that we don't have to wait (up to) one year for all your hard > work to be marked stable but I'm sure this has been debated before in which > case ignore that comment. > > Thanks, > > Jamie > > -- > 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 > -- 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
