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.

Yes but as we include different 'states' of these bundles making the
differences obvious in the PR release cycle can be beneficial for
newcomers.
You can easily review the changes between one version and the other.
I agree it's weird to impose that on those 'vendors' so we could fork
those projects and tag them in our version of the repo.

> Assetic is a separate project which is not tied to Symfony so why should
> it contain tagged releases for Symfony releases ?

No, it shouldn't be on the same release cycle I'm just saying it would
be nice to use a certain tag in the distribution.

> 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)

It's not about code management, it's about review and making changes
visible in a nice way.
I'm well aware that downloading the tarball is the recommended way to
download PR releases.

Again, it's most important to me for the docs repo!

>
> --
> 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

Reply via email to