PyroCMS, it's first-party addons, and the Streams Platform all maintain a Semantic Versioning convention:
Patches may be released as often as every week. Patches will never contain breaking changes.
Minor releases will be released as communicated (usually every 4-6 months) and will also never contain breaking changes to standard installations but may require database migrations. Minor version changes may also contain small changes necessary to custom extensions or overridden configuration for example; however these changes will always be communicated through release notes.
When referencing the Streams Platform or addon packages from your
composer.json, you should always use a version constraint such as
~1.6.*, since patches are safe and minor versions may include migrations.
Major releases are separated by years and represent fundamental shifts in the framework's architecture and/or conventions. Currently, there are no major version changes in development.
For LTS releases, such as PyroCMS v3.8, bug fixes are provided for 2 years and security fixes are provided for 3 years. These releases provide the longest window of support and maintenance. For general releases, bug fixes are provided for 6 months and security fixes are provided for 1 year. For all first-party addons, only the latest two releases receive bug fixes.
Version 3.8 brings in Laravel 8. We have finished removing problematic services and dependencies and have loosened dependencies from the core to help usher in a longer more flexible future of the PyroCMS v3.x branch.
Streams Platform 1.8
Our application engine has been updated to remove problematic dependencies and services like asset compiling. Miscellaneous bug fixes have been addressed.
The Streams Module, formerly a PRO addon is now included.
Data modeling is a core concept of PyroCMS. It is THE fundamental concept of Streams 2. Including the Streams Module out of the box feels right.