[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Origin EOL policy and what does trigger a new minor release


I'm sending out this email to understand what is the Origin EOL policy and also understand / start a conversation around what is considered critical bug which does trigger a new Origin minor release.

The rational started from [1] where after i migrated all my internal prod environments from 1.5.1 to 3.7.0 but due to bug [2] was fixed in [3] i had to move to 3.7.2 (picked latest minor due to CVEs too).

Now after going to all that long/ painful (due to extensive maintenance window and few disruptions at apps level) upgrade process, i then got hit by [1] and as it stands today don't have many options on the table except forking and trying to back port the patch myself.

It will be naive to think that Origin will get all/ majority of the OCP bug fixes however i do expect to have a gate or a transparent/known (public) process which defines what critical bug is (same in how you might have for OCP) such that a new Origin can be triggered.


[1] https://github.com/openshift/origin/issues/19138
[2] https://github.com/openshift/origin/pull/17620
[3] https://github.com/openshift/origin/releases/tag/v3.7.1

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]