LDAP Upgrade process is a micro schema version change

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.3.X, Master
• Fix Version/s: 7.3.10 DXP FP1, 7.3.10.1 DXP SP1, 7.3.6 CE GA7, 7.3.X, 7.4.13 DXP GA1, Master
• Component/s: Application Security > LDAP, Database Upgrade Framework
• Labels:
  • NAT
  • liferay-dxp-73-sp1
  • liferay-fixpack-dxp-1-7310
  • pt-upgrade-review
• Branch Version/s:
  7.3.x
• Backported to Branch:
  Committed
• Fix Priority: 4
• Sprint: Iteration 49
• Git Pull Request: https://github.com/achaparro/liferay-portal/pull/734

The upgrade process added in LPS-119816:
https://github.com/liferay/liferay-portal/blob/master/modules/apps/portal-security/portal-security-ldap-impl/src/main/java/com/liferay/portal/security/ldap/internal/upgrade/LDAPServiceUpgrade.java#L35

Shouldn't be a major upgrade because it's solving a bug and that means that contains schema/data changes that are compatible with the latest version of existing code.

Check the following article to get more information:
https://help.liferay.com/hc/en-us/articles/360017889792-Meaningful-Schema-Versioning
or
https://grow.liferay.com/people/Upgrade+Process+-+Schema+Version+Definition

It's crucial to follow these rules, otherwise we are forcing customers to execute the upgrade tool anytime we need to backport these changes. To avoid that we will have to create a dummy upgrade process in master from 0.0.1 to 1.0.0 to be able to backport and execute this upgrade from 0.0.0 to .0.0.1 in 7.2.x

cc/ marta.medio