Symfony 2.2 Schedule Update
First, and foremost, I would like to wish you, the wonderful Symfony community, the best for 2013. Enjoy your work, enjoy your family, enjoy your friends, ... enjoy using and contributing to Symfony!
Let's get back to business now. As part of the Symfony 2.2 release process, we will release the first beta of Symfony 2.2 tomorrow. As with any beta versions, the code is not stable yet; but having a package out of the door will give the opportunity for more people to test it out and report bugs and backward compatibility breaks on real-world projects.
This first beta also marks the end of the development period for Symfony 2.2; we are now entering the stabilization period for 2 months. It means that we won't accept any new features for Symfony 2.2 as of today (see below for some specific exceptions).
If you want to help us out, try to upgrade your Symfony 2.1 applications by following the UPGRADE instructions (and here are the ones for the Standard Edition). If something is not clear enough in the UPGRADE files, if there is something missing, or if your application does not work anymore after upgrading, consider posting your problem on the mailing-list, or submitting an issue; we have two months to polish everything so that upgrading when 2.2.0 stable comes out will be as easy as possible. Of course, keep in mind that running the upgraded application in production is not recommended.
What now? During the next two months, the community should focus on stabilizing Symfony 2.2: reporting bugs, reporting undocumented BC breaks, fixing bugs (have a look at our list of easy picks), updating the documentation (the official one but also all the numerous blog posts about Symfony2 out there), updating your bundles, writing about the new Symfony 2.2 features, ... Of course, you can work on new features, but we won't have a look at them before 2.2.0 final is released (if you want to submit a pull request, don't forget to tag it with `[2.3]` in the title).
Some of you are probably wondering why we are releasing a beta version and not a release candidate? That's because there are quite a few issues that we want to fix before (and they might have an impact on the current features):
- adding support for the recently adopted PSR-3 logger interface;
- re-evaluate some of the BC breaks we have done to avoid big impacts on your code (this is mostly for the Form component and also this pull request about sub-requests);
- some pull requests that are ready but not merged yet (this will be done this week).
If everything works according to the plan, the first release candidate should be released by the end of January. Speaking of dates, here are some other important ones you need to keep in mind:
- End of January 2013: End of maintenance for 2.0 (Symfony 2.0 being the first Symfony2 release enjoys a very long period of maintenance of 18 months);
- End of February 2013: Release of 2.2 (and start of 2.3 development);
- End of April 2013: End of maintenance for 2.1;
- End of Mai 2013: Release of 2.3 (the first LTS).
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.