-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: 7.0.0 DXP FP86, 7.0.10.12 DXP SP12, 7.0.X, 7.1.10 DXP FP14, 7.1.X, 7.2.10 DXP FP2, 7.2.10.1 DXP SP1, 7.2.X, 7.3.0 CE GA1, Master
-
Component/s: Database Upgrade Framework
-
Branch Version/s:7.2.x, 7.1.x, 7.0.x
-
Backported to Branch:Committed
-
Epic/Theme:
-
Git Pull Request:
This is the definition of the minor schema version changes:
MINOR: when you make a schema/data change that is compatible with the previous version of the code. These kinds of changes differ from micro-changes in that the modification is required for the new code to work (Ex: adding a new table/column without modifying the current data)
In this ticket we will modify the Upgrade Framework to allow:
- Working with the old version of the code even when new minor upgrade processes were executed.
- Require minor changes to be executed before using the portal.
After this, we have to:
- Update our tests
- Update the documentation
- Update the guide which explain the rules for the formula MAJOR.MINOR.MICRO regarding schema version changes (upgrade processes): portal.liferay.dev/docs/7-1/tutorials/-/knowledge_base/t/meaningful-schema-versioning
- causes
-
LPS-101860 SF error in PortalUpgradeProcess
- Closed