On Sat, Jul 30, 2011 at 10:45:27AM +0200, Micha? Piotrowski wrote:
> For example - release minor 2.{1,2,3..N} versions half-yearly
> with the half-year support.
> Symfony2 develops so well. I think that shortening the release cycle
> would keep this wonderful development momentum.
Short version:
Keep API/ABI, fix bugs and add *new* features so that
new minor versions are drop-in replacements.
Rant:
One thing is to learn, another one is to be able to use and maintain
it, maybe over many years.
If upgrading from one minor to another is too much work and even
may break third party bundles you will not like doing this twice a year.
Even changes that were done between betas in the Sf2 development
were bigger than should happen in a minor release, especally if it's
a half year release cycle.
For a freamework people actually make huge applications around, stability
and maintainability is a key issue, knowing that it will be bug and security
fixed for as many years as possible is a decider.
Symfony 1.4 will be maintained until november 2012 and that's not too bad
but the path from 1.0 to a maintaineable 1.4 application has not
always been easy and if you used a third party plugin, even worse and
close to impossible for many (if they didn't bother to release new versions)
So, too many releases is not really a feature when it comes to frameworks
unless you are certain that a new minor version is a drop-in replacement.
Doctrine seems to have managed to do this between 2.0 and 2.1, at least
where I have done the upgrade and if "we" can do the same, I will be
happy.
Thomas.
--
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
