search

Zauberfisch / silverstripe-boilerplate

Boilerplate template to quickly kick off a new SilverStripe project
21 stars 3 forks source link

Unstable SS build? #18

Closed bruce133 closed 10 years ago

bruce133 commented 10 years ago

It seems to me that the boilerplate is configured to fetch the latest unstable version of SilverStripe, is this correct? If so, what's the reason for not using stable?

PS. Unsure whether this is the preferred way to post this question - let me know if otherwise.

Zauberfisch commented 10 years ago

indeed, this boilerplate fetches SilverStripe latest by default. The reason for this is that in my opinion the usual stable releases are just as buggy as master, but master has more features and the latest fixes.

Furthermore I often end up writing fixes for SilverStripe myself and to do that properly, I need to be on latest codebase.

If you want a different version, you can simply modify the composer.json But I see the point that some people might want to have a different version of SilverStripe, I will think about this issue.

Zauberfisch commented 10 years ago

and, yes, github issues are perfect to raise such topics and discuss them.

bruce133 commented 10 years ago

Ah, I see.. I actually tried to modify composer.json, but didn't manage to fetch a different version. But no matter, if what you say is true then it's probably better to keep it as it is.

Zauberfisch commented 10 years ago

for the record: if one wishes to fetch a specific version of SilverStripe, simply set the version in composer.json to the desired version (NOTE: the versions in the composer.json are not SilverStripe releases, but actually composer tags so to speak, a list of these can be found here: https://packagist.org/packages/silverstripe/framework)

example:

"silverstripe/cms": "3.0.8",
"silverstripe/framework": "3.0.8",

or: 

"silverstripe/cms": "~3.0",
"silverstripe/framework": "~3.0",

further documentation on composer versions: http://getcomposer.org/doc/01-basic-usage.md#package-versions