Message of the day:
Welcome to SilverStripe | Current stable: https://goo.gl/C4F1T9 | Feature requests: https://goo.gl/EcQ34L | Community Forum: https://forum.silverstripe.org | StripeCon EU 2019! https://stripecon.eu
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
@Juan de la Cruz Talk like a pirate day is on September 19th 😂 https://en.wikipedia.org/wiki/International_Talk_Like_a_Pirate_Day
happy speak like a pirate day. could use some help in #translations. arghh
SemVer clearly describes it: >>> Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
Any enhancement is a minor
I guess it can be defined, somehow… but I find it hard
in the back-end? on the front-end? new SS version? new theme?
perhaps the difference between "new functionality" vs "changed functionality"?
for people using semver to version website releases, how do you define which changes are major or minor?
a major is better described as "API breaking" - changes are incompatible with the current API.