Le 02/05/2013 19:13, Fabien Potencier a écrit :
On 5/2/13 2:57 PM, Lukas Kahwe Smith wrote:
On Mar 14, 2013, at 20:53 , Lukas Kahwe Smith <[email protected]>
wrote:
Ahoi,
I guess with "symfony/symfony": "2.3-dev as 2.2" I would only have
an alias on "symfony/symfony", but I would need to have separate
alias for each specific component if I want to start testing f.e. a
bundle that depends on another bundle that in turn has not yet
allowed dev-master?
@Jordi/Stof: could one of you show me how I could for example test
https://github.com/symfony-cmf/TreeBrowserBundle with 2.3?
I mean I can change the dev deps of the Bundle itself to
">=2.1,<2.4-dev" but then I would need to set an alias for all
dependencies f.e. of DoctrineBundle to also allow for 2.3 there ..
right?
Warming up this topic as I am getting more and more users that say
that I should just use ~2.1 etc. as dependencies for Symfony2 related
stuff since with 2.3 there will be no more BC breaks. I guess for 2.3
this should be true .. but for 2.4 there will be at the very least be
feature additions that at times can cause issues. So where do we
stand here as a community?
I think there is several possible answers depending on a lot of
different factors.
For most components (like BrowserKit, ClassLoader, Console,
CssSelector, DependencyInjection, DomCrawler, EventDispatcher, Finder,
Process, Yaml), it should be safe to rely on ~2.1 or ~2.3. Breaking BC
here is highly improbable and should be fight at all cost.
For some other (bigger) components (HttpFoundation, HttpKernel,
Security, Templating, Serializer, Validator, Form), we should not
break BC. But as they bigger, we might add more features over time and
depending on them would change your range of acceptable versions.
Adding a feature means that bundle might want to bump the requirement in
their next release if they rely on it. It does not mean that existing
versions of the bundle cannot work with 2.4 (they will simply not use
the 2.4 features).
The only thing that would cause issues for bundles relying on ~2.1 or
~2.3 is if the component breaks BC on a method they are using. Given the
next rule, it should be safe even for bigger components.
In any case, keeping BC should be our top one priority from now on.
Fabien
--
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 [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
---
You received this message because you are subscribed to the Google Groups "Symfony developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
