Le 19/09/2012 23:09, Florin Patan a écrit :
What about the release of separate components / bundles shipped with
Symfony Standard? How would that be handled?
Currently if a component needs an upgrade, say for a security patch,
then a new release needs to be done, if I'm right, which basically
goes against the idea of having the framework as a group of components
glued together.
Maybe a solution like patch-levels, I think composer supports a
version like : x.y.z.a and if needed add the changes to composer to
support this type of updating as well?
Regards,
Florin
composer supports 4 level of numbers for the version number.
But anyway, if people are using composer, update from a maintenance
release to the next one is simply a matter of running "composer update"
without changing anything else, and security patches should also be
included in a maintenance release for the current branch, not only in
the next .y release.
--
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 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
