Commit 261cac71 authored by Pierre Smeyers's avatar Pierre Smeyers
Browse files

doc(archi): non-backward compatible features

parent 03b4d4cb
Loading
Loading
Loading
Loading
+17 −0
Original line number Diff line number Diff line
@@ -110,3 +110,20 @@ Examples:
## Dotenv artifacts

Propagate dynamic output variables to downstream jobs...

TODO - TODO - TODO

## Preserve a reasonable rollout time before implementing non-backward compatible GitLab features

Some GitLab features are not backward compatible. 
For instance features that introduce a new keyword that would break the `.gitlab-ci.yml` validation on 
previous versions of GitLab.

In that case, _to be continuous_ templates shall observe a _reasonable_ rollout time before implementing
them, not to break projects using them on a self-managed server.

For security patches, GitLab [maintains the two previous `major.minor` versions](https://docs.gitlab.com/ee/policy/maintenance.html).
We decided to observe the same delay before implementing a non-backward compatible feature.
I.e. wait that the GitLab version that introduced the feature is the oldest version maintained by GitLab.

In practice, this is about 3 months.