Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Releases and Announcements /

Latest news about the SilverStripe software.

Moderators: martimiz, Sean, Ed, biapar, assertchris, Willr, Ingo, swaiba, Graves

SilverStripe 3.2.0 beta1 release announcement


Go to End


3 Posts   2022 Views

Avatar
tractorcow

Community Member, 63 Posts

19 June 2015 at 8:13pm

Edited: 19/06/2015 8:15pm

SilverStripe 3.2.0 beta 1, the long awaited, has finally been released.

The changelog, upgrading notes, and other important information is available on the release notes page at http://docs.silverstripe.org/en/3.2/changelogs/beta/3.2.0-beta1/

To get setup, you can install this using composer (as below):

    composer create-project silverstripe/installer ./ss32 3.2.0-beta1

You can also download pre-built zip / tar from http://www.silverstripe.org/software/download/ under "Pre releases".

Please try this out and give us as much feedback in time for beta2, which we hope to release in about one months time.

Thank you everyone who has helped to contribute to this project!

Kind Regards,

Damian Mooyman | Senior Platform Developer
SilverStripe

Annoucement: https://groups.google.com/forum/#!topic/silverstripe-announce/CYWO2k-yxBo

Avatar
kjm87

Community Member, 1 Post

24 June 2015 at 10:23pm

Have you been testing this release against PHP 7?
That is would you expect people to be able to use SilverStripe 3.2 and PHP 7 once both are in production?

Avatar
Pyromanik

Community Member, 419 Posts

25 June 2015 at 8:03am

I do not believe so, as PHP7 expressly forbids class names such as 'Float', 'Int', etc. Silverstripe contains such named classes, and to alter that would break backwards compatiblity (would require a major version number adjustment - i.e. v4.0).
I'm sure it is well noted and on the development horizon, but for now (with 3.x) I do not think it feasible.