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
Copy file name to clipboardExpand all lines: src/faq/faq-eol.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,8 +82,8 @@ Non-LTS feature releases will be allowed access to download signatures until at
82
82
83
83
| Feature release | First Published | Latest patch version | Expected End of Life (EOL) | Signature load testing until | Signature FP testing until | DB downloads allowed until | Patch versions continue until |
@@ -122,8 +122,8 @@ If the non-disclosure / release date for a security patch falls within four (4)
122
122
>
123
123
> In this situation, we would prepare a security patch version for:
124
124
> - the 1.6 feature release (e.g., 1.6.1),
125
-
> - the 1.5 feature release (e.g., 1.5.3),
126
-
> - and the 1.4 LTS feature release (e.g., 1.4.5).
125
+
> - the 1.5 feature release (e.g., 1.5.4),
126
+
> - and the 1.4 LTS feature release (e.g., 1.4.6).
127
127
>
128
128
> Once the critical patch versions have been published, the same or equivalent fixes will be merged into the `main` branch for inclusion into the next feature release (1.7.0).
129
129
@@ -135,6 +135,6 @@ If the non-disclosure / release date for a security patch falls after four (4) m
135
135
>
136
136
> This would exceed our 4-month policy, so we would publish the fix:
137
137
> - in 1.6 (eg. 1.6.1),
138
-
> - and the 1.4 LTS feature release (e.g., 1.4.5).
138
+
> - and the 1.4 LTS feature release (e.g., 1.4.6).
139
139
>
140
140
> ... but would not publish a patch version for the 1.5 feature release.
0 commit comments