On 9/19/12 11:40 PM, Florin Patan wrote:
I was thinking to upgrade to a .a revision level rather that release a
maintenance version sooner that planned/wanted.
Think for example if something appears in the YAML component and needs
to be patched asap but at the same time you want to wait for a certain
event to happen before releasing the maintenance version, like a work in
patch for Process component.
If the YAML or the Process component need a patch to be released ASAP,
we just release the whole Symfony package. That's what we've been doing
for quite some time now and it works well.
Something like Ubuntu has for PHP for example. They ship a version of
PHP, current is 5.3.10 but then they have the patch level so that they
can still ship updates to that version without upgrading the PHP smaller
increment version and thus creating confusion among users. This might
not be the case for now but when going for LTS would you be doing small
maintenance release as soon as needed with the whole framework or just
bump the component needed?
Regards,
Florin
On Thursday, September 20, 2012 12:19:41 AM UTC+3, Christophe COEVOET wrote:
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 [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
