Embed Size (px)
Citation preview
SilverStripe 3.2
11 June, 2015 • London • Dan Hensby (@dhensby)
What’s new in 3.2 and how you can help us launch
An introduction to
What’s new in 3.2?
● Big changes● PHP min version bumped to 5.3.3 (from 5.3.2)● Parameterised DB queries! PDO connector now
standard (use it!)● SiteConfig and Reports moved to separate
modules● Introduced “Archive” concept for pages (superseding
“delete from draft”)
It’s rhyme time
11 June, 2015 • London • Dan Hensby (@dhensby)See the changelog: bit.ly/ss32changes
What’s new in 3.2?
● Lots of minor changes and improvements● FormField::validate() implemented more
consistently● Speed improvements (Config caching - LRU
replaced with Key-Value store)● DataObject changed fields constants added
(CHANGE_STRICT, CHANGE_VALUE, CHANGE_NONE)● $FromEnd template helper added● Various UX improvements like a fancy new loader
GIF11 June, 2015 • London • Dan Hensby (@dhensby)See the changelog: bit.ly/ss32changes
What’s old in 3.2?
● Removed● <% control %> syntax in templates (use loop)● Profiler class● Member login tracking● DataExtension BC with 2.4 (extraStatics(), etc
removed)● A few more minor classes
● Deprecated (still works, but will be removed later)
● Config setters● DB class functions brought inline with naming
conventions
Things that are gone (or going)
11 June, 2015 • London • Dan Hensby (@dhensby)
How hard is it to upgrade?
● MySQLDatabase seems to have some memory issues - use MySQLPDODatabase
● Big re-write - lots of changes - see the changelog for a complete guide
● Prepared queries - *droooool*● SQLSelect, SQLDelete, SQLUpdate and SQLInsert
Effort involved to move to 3.2
11 June, 2015 • London • Dan Hensby (@dhensby)
How hard is it to upgrade?
● Form IDs have had various fixes● IDs for FormFields are now “namespaced” to reduce
ID collisions● Forms no longer produce invalid IDs● Removed duplicate IDs from inputs and their parent
div● Upgrade pain for projects that rely on Form/Field IDs● Legacy support for anyone who needs old
behaviour:
Effort involved to move to 3.2
11 June, 2015 • London • Dan Hensby (@dhensby)
Wait, aren’t we SemVer now?
● SemVer defines a specification for versioning
● Major . Minor . Patch● Composer replies on SemVer (~3.2.1
means 3.2.x - low risk upgrades)● Officially adopted in late 2014● First minor release since then● Upgrading should be relatively smooooth
Our first “minor” release since adopting Semantic Versioning
11 June, 2015 • London • Dan Hensby (@dhensby)See semver.org for specifications
When’s it coming?
11 June, 2015 • London • Dan Hensby (@dhensby)
3.2.0-beta.1
11 June, 2015 • London • Dan Hensby (@dhensby)
Out next week!
How can you help?
● Get using it● composer create-project silverstripe/installer:3.2.x-dev www
● Upgrade a project you’re currently developing (with release a month or so away)● composer require silverstripe/cms:3.2.x-dev --update-with-dependencies
● Submit tickets to /issues● Submit patches and improvements to /pulls
Getting to RC1 quickly
11 June, 2015 • London • Dan Hensby (@dhensby)
