3.2 stable finally final

It's been a long cycle since the first beta of 3.2 was available in June 2015, but a few months later we finally have a stable release available for download. This will mark our first new minor release of SilverStripe CMS since our adoption of semantic versioning in November of 2014.

Over the next few weeks we will be working hard to improve support and verify compatibility of our existing supported modules with 3.2, ensuring that users relying on critical features will be supported during the upgrade process.

Why should I upgrade to 3.2?

There are a few large features designed to bring the maximum benefit to SilverStripe developers. Some of these include:

• New batch actions and tools for managing multiple pages.
• A new parameterised database ORM to prevent SQL injection.
• New standard support for PDO.
• Modularised reports and siteconfig components.

For more details on the new features included in 3.2, take a look back at the beta release blog post. 

How do I upgrade to 3.2?

If you're using composer, you can adjust your composer.json as below and run `composer update` to get the new version.

{
	"require": {
		"silverstripe/framework": "3.2.0",
		"silverstripe/cms": "3.2.0",
		"silverstripe/siteconfig": "3.2.0",
		"silverstripe/reports": "3.2.0",
	}
}

You can also download a packaged zip or tar.gz from the SilverStripe software downloads page.

We also advise users running on servers with PDO available to activate the new PDO connector for MySQL. If you are configuring your database credentials via an _ss_environment.php file, update the database as below:

define('SS_DATABASE_CLASS', 'MySQLPDODatabase');

What about 3.1 I love it so much?

For quite a while 3.1 has been given primary focus, and it's not going away just yet. 3.1 will receive security patches and critical fixes for quite some time. However, the best place to put your code from now on will be on 3.2, as this will receive the most frequent patches, updates, and releases.