New field: versionLag

[krissmed]

Tell us more.

Hi,

I have a use case that I can’t solve with the current functionality.

Use case

I use a package that supports the following releases: 1.10.x, 1.9.x, 1.8.x, and 1.7.x. It will always provide patches and backport changes to the current version minus three minor releases. I want to stay as far behind as possible within the supported version to always be on a thoroughly supported version.

Examples of packages that follow this strategy:

Longhorn – https://github.com/longhorn/longhorn/wiki/Release-Schedule-&-Support
GitLab – https://docs.gitlab.com/ee/policy/maintenance/

Proposed fix

Add the following fields:

minorVersionLag: The number of minor releases you will stay behind the latest.
majorVersionLag: The number of major releases you will stay behind the latest.

[jamietanna]

Let's move conversation into #42376, which is an existing request