Roadmap

Our next major version of SilverStripe will be 3.1:

 

Our next minor version of SilverStripe will be v3.0.3

 

How do I interpret the Release Tickets?

Our software is developed and released in a public, open source, and collaborative manner. Many features and fixes are done by SilverStripe Ltd, other work is contributed by our community, and everyone is involved in ideas and discussions. This means the timing and features of a release are subject to frequent change. What we can do is ensure all components are publicly visible, described when done, and labelled if they're likely to be worked on. Each release comprises hundreds of tickets. Each ticket is given a status and a severity, which can be read as follows:

  • Closed: Included in the release.
  • Started: Probably included - particularly if the severity is high.
  • New / Assigned: Might be included; the higher the severity, the higher the probabiltiy.
  • Not listed - Some features and bug fixes are contributed without being first listed on the release plan, and would be placed on the milestone as a closed item. 
  • If you want a feature or bug completed, the best thing to do is to provide us with the code. (Changing the milestone field of a ticket doesn't do anything). Alternatively, add a comment to the ticket, and if necessary, escalate the discussion to the SilverStripe Development Google Group

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.