Hi all,
As you might know, We are in the process of moving most protected
properties/methods to private and the conversion is almost finished. If
you think something need to be moved back to protected, please explain
your need and we will consider it or we will provide a better extension
point (that's what we've already done for the Console component --
instead of moving a set of methods back to protected, we refactored the
code and created a cleaner extension point).
The next step is to tag the API (classes/methods/properties) for which
we will guarantee BC for all 2.x versions. It means that the name, the
behavior, and the signature won't change. So, basically, if you only use
this API, your code should/must work with all 2.x versions (the only
exception will probably be for security problems or PHP forward
compatibility).
This BC API will be tagged with @api in the phpdoc (as done by the Flow3
team). As this is a strong commitment, we will start with a relative
small API for 2.0 and I hope that a complete stable API can be designed
for 2.1.
To give you a gist of what it is all about, I've tagged the ClassLoader
and CssSelector components. The CssSelector component is interesting as
it only contains one class and one method tagged with @api (everything
else is really not public and even if some methods are public because we
need them internally, you should never ever use them).
Fabien
--
Fabien Potencier
Sensio CEO - Symfony lead developer
sensiolabs.com | symfony.com | fabien.potencier.org
Tél: +33 1 40 99 80 80
--
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
