Symfony's biggest change was likely in August (massive namespace/class renaming), and *crosses fingers* we shouldn't see anything on that scale again - but you'll certainly have no assurance of that. Fabien has recently been implementing new features quite regularly in his own github repository and then pushing to symfony's master. On top of this, you have the public release branches (PR3 being the latest), which are typically kept in sync with the symfony-sandbox repository -- since there aren't any console commands to initialize projects/apps at the moment, the sandbox is quite helpful.
I'm aware of two large-ish companies using Symfony2 already, OpenSky <http://shopopensky.com/> is mostly all running atop Symfony and is doing development in-house (I'm here now :). There's also Exercise.com <http://www.exercise.com/>, which has hired knplabs <http://github.com/knplabs> of Diem/Symfony1 fame to assist in developing their entire CMS/community platform. Depending on how you want to allocate your time, you may end up going a month without merging in upstream progress. Or, you might prefer to set aside Friday's to integrate new changes. I don't think you'll find things that are horribly broken, though - so it's quite easy to continue with your own development on outdated Symfony2 code without missing much. At OpenSky, our last big merge took about 1.5 weeks of developer time to merge in 1.5 months of Symfony changes (this include the nasty August update I alluded to). The best advice I can give is: unit tests are your friend. The time invested in writing tests will pay for itself once you merge in changes and immediately see test failures instead of having to do QA rounds in a browser hunting for 500 errors or worse, obscure bugs. Documentation isn't too much of an issue unless you're diving into the internals. Fabien and company have already added some great starter docs on the Symfony2 website (much better than the 4-page tour that existed before July). Doctrine ORM/ODM documentation is also in a decent place (and their API is less likely to change IMO). Perhaps the thing most missed will be community plugins. There's quite a few to be found already via <http://symfony2bundles.org/> but some currently fill gaps for essential Symfony2 components that are still in the pipeline (e.g. Fabien is still deciding how to implement the security component). Given that, if you were to utilize knplabs' DoctrineUserBundle right now, you might find yourself having to adapt that down the line once security is implemented as a first-class Symfony2 citizen. On Sep 16, 9:01 am, Donald Tyler <chekot...@gmail.com> wrote: > Hi everyone, > > I've been following the development of Symfony 2 since it was announced, and > I would like to try it out with a real project I'm working on. It seems to > be coming along very nicely, and I'd really like to try building something > with it. Now, I know that it's not "production ready", and the planned > release is not for another 6 months. But given that, I'd like to know the > following: > > How stable is it? Is it stable enough to start a project now, and gradually > work on it until symfony 2 is released? > > What is the rate of change? If I start building a project now, am I going to > have to constantly rewrite large portions due to API changes? > > What kind of challenges should I expect to face if I were to build a project > using Symfony 2 at this time? > > Thanks in advance for the advice. > > - Donald -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
