Remove refactoring.rename.useAtomicRename property and old rename code

Development
#1

Hi everyone,

I’m opening that vote to propose dropping the property refactoring.rename.useAtomicRename which is true by default and to completely remove the code that is called when the property is false.

The rationale is that this property has been created in 12.5RC1 to ensure to have a fallback in case of problems with the new mechanisms. To be clear the documentation for that property state that:

This property aims at being removed in the future once the atomic rename has been validated to work 100% fine.

Now we don’t test anymore the code when using the old mechanism, and we probably fixed bugs with the new rename mechanism that still exist with old one. So basically we don’t support anymore the old mechanism.

There’s 2 votes to perform here:

  1. Are you ok to drop this (property + code) for 15.5.x
  2. Same question for 14.10.x

This vote is opened for 1 week until wednesday 21st so that we can do it for 15.5.x.

Here’s my +1 for both votes.

#2

+1 for both (since I think using false might cause some bugs, see Moving a page loses translation)

#3

+1 for both.

Thanks,
Marius

#4

+1

+0

#5

+1 for both

#6

+1 for both

#7

Closing this vote with 5 +1 to remove it for 15.5 and 4 +1 to do it for 14.10.x
I opened Loading... for it.

Thanks