You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
30 lines
1.2 KiB
30 lines
1.2 KiB
2 years ago
|
********
|
||
|
|
Releases
|
||
|
|
********
|
||
|
|
|
||
|
|
Versioning
|
||
|
|
==========
|
||
|
|
|
||
|
|
Script Tease follows a loose form of `semantic versioning`_. The use of semantic versioning makes it clear when deprecation occurs and backward compatibility is removed. Documented incompatibilities may still exist where deprecation is not feasible (technically or financially).
|
||
|
|
|
||
|
|
.. _semantic versioning: https://semver.org/
|
||
|
|
|
||
|
|
Cadence
|
||
|
|
=======
|
||
|
|
|
||
|
|
New features (and especially new overlays) are planned for release every 3 months. Patch-level changes (to fix bugs or security issues) are always released as needed.
|
||
|
|
|
||
|
|
Long-Term Support
|
||
|
|
=================
|
||
|
|
|
||
|
|
Some releases may be designated as long-term support (LTS) releases. Such releases will have security and critical bug fixes applied for 6 months.
|
||
|
|
|
||
|
|
Deprecation Policy
|
||
|
|
==================
|
||
|
|
|
||
|
|
Minor releases may deprecate features from a previous minor release. For example, if a feature is deprecated in release 1.1, it will continue to work in the 1.2 release, though warnings may be raised. However, the deprecated feature may be removed in release 1.3 and may not function as previously expected or will raise errors.
|
||
|
|
|
||
|
|
Major releases may *always* remove deprecated features.
|
||
|
|
|
||
|
|
Patch-level releases *never* remove deprecated features.
|