How do I interpret the release milestones on GitHub?
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. Milestone tickets on github.com have a status (open or closed), and can be flagged.
- Closed: Included in the release.
- Open and Unassigned: Might be included
- Open and Assigned: Probably included, particularly if flagged "critical" or "blocker"
- If you want a feature or bug completed, the best thing to do is send us a pull request. Alternatively, add a comment to the ticket, and if necessary, escalate the discussion to the SilverStripe Development Google Group.
How does the release process work
- Merge: Update translations, merge old fixes into latest release versions, and last minute code cleanup.
- Test: Test locally to make sure everything is working as it should.
- Document: Ensure all changes and considerations are communicated to upgrading users via the upgrading notes.
- Release: Push “Go” button.
- Publicity: Tell the world though the SilverStripe announce group and blog.
Want announcements of new releases to the SilverStripe codebase and modules?
Join our Release Announcements Google Group.
Upgrading and changelog
Keep an eye on security advisories and changes to installed modules. A changelog is also included with each new release and outlines all historical changes included in the latest version of software. Composer helps manage these changes and allows you to focus on developing rather than upgrading.