I would vote for releasing the new version soon. Reason is that there are 
many differences between version 2.0 and 2.1.
If you are able to release the 2.1 version soon (with everything which is 
done till now and working) and the new features that are unstable 
to be postponed for next revision 2.2. 

Take this for an example: developing a SF2 site which should be long life 
supported should always follow the new official release (and not beta 
releases).
If 2.1 version is postponed every website built in the next 3 months for 
example will have to go through Framework update and 3rd party bundles 
update.
And there will be alot problems with 2.0 bundles updated to 2.1 bundles. ( 
or even worse, currently there are bundles for the 2.1 version will alot 
more options than the 2.0 onces)

Getting the 3rd party bundles working good for the new version could be 
tricky, could take time and alot of factors can affect.
What will happen according to me is that even if the Framework is perfectly 
done in 3 months and ready for the release of the new version,
bundles won't be... and getting 2.1 site to work could take up to 4 months 
or even more for large project with many 3rd party bundles.

Now what will happen if the new version is prepared and released soon. 
Every developer starting a new project will pick the new version.
Broken bundles will be fixed very soon after that. Everyone is happy.

Going from such 2.1 version to 2.2 version shouldn't be a pain and BC 
issues should be taken is a must needed evil to get the thing going in 
right direction :)








-- 
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

Reply via email to