Not a bug Serialised fields to JSON upgrade steps duplicated

[Naz]

Affected version

2.1

Is there a particular reason why the serialized fields to json upgrade steps are duplicated in the 2.1 alpha steps and then the 2.1 beta 2 steps? I realize the issue the other week necessitates running them again to ensure everything is converted but I'm not really seeing the benefit of running them twice. Instead, it seems to create avoidable overhead.

 

[Mike]

The issues noted week are the cause. There were more subtle issues discovered than originally realized--plus indications of people upgrading production sites--that we felt this was the best course. Re-running the steps is the only way to ensure that all data was converted if you had already upgraded to beta 1. (Note that not all of the steps can be re-run in the alpha upgrade script as there are other schema changes after them.)

You will likely see a change in this script closer to a stable release such that it doesn't get run twice if we think you already converted with the existing code.