add notes on laravel version scheme

Author: taylorotwell

Diff for: releases.md

@@ -1,5 +1,6 @@
 # Release Notes
 
+- [Versioning Scheme](#versioning-scheme)
 - [Support Policy](#support-policy)
 - [Laravel 5.4](#laravel-5.4)
 - [Laravel 5.3](#laravel-5.3)
@@ -11,6 +12,21 @@
 - [Laravel 4.2](#laravel-4.2)
 - [Laravel 4.1](#laravel-4.1)
 
+<a name="versioning-scheme"></a>
+## Versioning Scheme
+
+Laravel's versioning scheme maintains the following convention: `paradigm.minor.patch`. Minor framework releases are released every six months (January and July), while patch releases may be released as often as every week. Patch releases should **never** contain breaking changes.
+
+When referencing the Laravel framework or it's components from your application or package, you should always use a version constraint such as `5.4.*`, since minor releases of Laravel do include breaking changes. However, we strive to always ensure you may update to a new minor release in one day or less.
+
+Paradigm shifting releases are separated by many years and represent fundamental shifts in the framework's architecture and conventions. Currently, there is no paradigm shifting release under development.
+
+#### Why Doesn't Laravel Use Semantic Versioning?
+
+On one hand, all optional components of Laravel (Cashier, Dusk, Valet, Socialite, etc.) **do** use semantic versioning. However, the Laravel framework itself does not. The reason for this is because semantic versioning is a "reductionist" way of determining if two pieces of code are compatible. Even when using semantic versioning, you still must to install the upgraded package and run your automated test suite to know if anything is *actually* incompatible with your code base.
+
+So, instead, the Laravel framework uses a versioning scheme that is more communicative of the actual scope of the release. Furthermore, since patch releases **never** contain intentional breaking changes, you should never receive a breaking change as long as your version constraints follow the `paradigm.minor.*` convention.
+
 <a name="support-policy"></a>
 ## Support Policy