You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
new minor version for the already known major version (like, 2022.1.1 once we already set latestStable to 2022.1): should update latestMinorsOfOldSupportedMajors or latestStable
first stable release of a new major version: should clean up eapOfLatestSupportedMajor (which will be typically present), update latestStable and append the former latestStable to latestMinorsOfOldSupportedMajors
I'd actually consider making the entire algorithm quasi-stateless, so that:
As a part of this task, I'd also update the docs in CONTRIBUTING.md (as they imply all the version updates are to be performed manually, which is/will be no longer the case)
Follow-up for #794.
Should check two things:
latestStable
to 2022.1): should updatelatestMinorsOfOldSupportedMajors
orlatestStable
eapOfLatestSupportedMajor
(which will be typically present), updatelatestStable
and append the formerlatestStable
tolatestMinorsOfOldSupportedMajors
I'd actually consider making the entire algorithm quasi-stateless, so that:
latestMinorsOfOldSupportedMajors
latestStable
eapOfLatestSupportedMajor
are computed based solely on:
earliestSupportedMajor
and NOT on the other existing properties.
This will make dealing with corner cases less painful in general.
The text was updated successfully, but these errors were encountered: