Hey Marijn- I think what you're talking about is a really good idea, but it's just too early to worry about that. Since we're not even at beta yet, the idea of tagging the releases of different libraries so that you know which is compatible with which just wouldn't be a good use of time.
Going forward,there will certainly be a version of the documentation tagged for Symfony 2.0, vs 2.1. I think you can expect to see that in all high-quality bundles as well (and you can yell at a bundle author if they're slacking). Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Thu, Mar 31, 2011 at 8:11 AM, Marijn <[email protected]>wrote: > P.s. Sorry if I came of a bit rough but I'm in a hurry and wanted to > reply to your email. I now realize I might have come off a bit > offensive, that is in no way my intention :-) > > On Mar 31, 2:51 pm, Christophe COEVOET <[email protected]> wrote: > > Le 31/03/2011 14:45, Marijn a crit :> Like I sad it's really too bad > that _besides_ the symfony repository > > > and the standard edition no releases are being tagged. > > > > > Repositories like FrameworkExtraBundle, SecurityExtraBundle, symfony- > > > docs, SecurityExtraBundle, Assetic etc. > > > > > symfony-docs being the most significant of course. > > > > Bundles repositories will tag their releases when they will be released. > > But releasing a bundle now is weird IMO as the framework is not stable > > yet which implies changing the bundle. > > > > Assetic is a separate project which is not tied to Symfony so why should > > it contain tagged releases for Symfony releases ? > > > > The tarball on the Symfony website comes bundled with the needed version > > of the vendors for a given state of Symfony. this is the recommended way > > to get the preview releases. The symfony-standard repository is kept in > > sync with Symfony master branch (as for most bundles) > > > > -- > > 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 [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 > -- 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 [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
