You might say that the 2.0.7 branch got off to a bit of a… rocky start. Soon after it was first released at the end of December, several issues were identified that affected upgrade paths and extension compatibility. Before long, it had become clear that 2.0.7 would need more work before it could be considered a stable release.
The team set about fixing the outstanding issues, and at the same time resolved to do a better job of managing the system’s development in the future. Today, we’re taking a first step in that direction by announcing the availability of the first official 2.0.7 Release Candidate.
Our goal is to have a release candidate period of roughly two weeks, during which the system can be rigorously tested and any remaining bugs fixed. Depending on the outcome of this period, we’ll either release the final version or follow up with a second release candidate.
Wondering what you can do?
1. Get It
2.0.7RC1 has been tagged on Github.
2. Test It
Community members can help make 2.0.7 as stable as possible simply by putting it through the wringer, so to speak. Install it, mess around with it, try to break it. If you’ve got existing websites running earlier versions of Symphony, create development copies and try upgrading them.
3. Update Your Extensions
Developers should use this period to test their extensions in 2.0.7 and make any necessary updates.
4. Report Bugs
If you find issues, report them.