--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at https://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
+1 For dropping IE10 and lower
We as an agency will have to continue to support our current and future clients on IE8 & IE9 and understand that SilverStripe 4 won't be the right fit for those clients. This does raise the question of how long SilverStripe 3 will continue to be supported? Which I think is also relevant to the issue at hand.
I'd have to echo this - much of our work is with local authorities and they are very stuck to IE9 and IE10 - I'm very happy to say I don't hear about older versions anymore.
It isn't about the smallness of the numbers when the bulk of those folk are in one group (i.e. local authorities) and are very unlikely to move forward quickly.
--
Swaiba said:I'd have to echo this - much of our work is with local authorities and they are very stuck to IE9 and IE10 - I'm very happy to say I don't hear about older versions anymore.
It isn't about the smallness of the numbers when the bulk of those folk are in one group (i.e. local authorities) and are very unlikely to move forward quickly.If you think about it though, since this is for a totally new (and as of yet unreleased) version of SilverStripe, they will be able to think about if they wish to use SS 4.x. One of the considerations the developer need to take into account is the fact that the primary user base for the CMS is still constrained to IE9 (for example). If that's the case, they should simply install the latest version of SS 3.x and ensure that the powers that be (primarily IT) are informed of the additional technical debt that they are incurring upon themselves by not upgrading to IE11 (if indeed it's worthwhile to really stick with SS 3.x), due to the backward incompatible API changes implicit in a major version change, should they ever decide to upgrade to SS 4.x ex post facto.
My assumption is that no major changes would be implemented that wouldn't be supported in the already defined list of supported browsers for that version anyway. At least that should continue to be the case. A
My concern is that SilverStripe 4 will be released and before SilverStripe 5 is released support for SilverStripe 3 will be dropped. This would leave our customers with no officially supported version of SilverStripe that they could access. Which would be a big problem for us.
--
What about the idea of SS adopting an Ubuntu style release cycle with LTS (Long term support) versions ?
Such a schedule would satisfy the needs of both Legacy Laggards and Bleeding Edgers. If SS3 were deemed LTS, then development on SS4 can ignore legacy issues altogether and push the envelope by using the latest and greatest, even experimental features.
We as an agency will have to continue to support our current and future clients on IE8 & IE9 and understand that SilverStripe 4 won't be the right fit for those clients. This does raise the question of how long SilverStripe 3 will continue to be supported? Which I think is also relevant to the issue at hand.