Comment 30 for bug 1858448

Modifications to my previous comments...

I propose we disable the feature entirely in the 3.4 series by commenting out / removing the code that migrates the data at circulation aging time and the code that performs the batch data migration in the upgrade script.

I propose we leave the schema changes in 3.4 though to avoid the need for 2 separate 3.5 upgrade tracks (one for those with the schema changes and one for those without). The schema changes will essentially be ignored in 3.4.

I also propose we perform no automatic data migration for 3.5, but instead provide instructions on how to migrate data for the 2 supported scenarios (age with circs, age by date).

I can create patches for these if this seems reasonable.