-
Type:
Sub-task
-
Resolution: Fixed
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: None
-
None
AT
Documentation to the migration guide is added
Reasoning
Even though migration guide documentation is not a hard requirement due to the reasons described here [1], I think it is not easy for the user to learn about the new features and derive which features cannot be used safely during a rolling update. This is why I tend to mention the feature in the migration guide and the implications.