Comment 35 for bug 1858448

I'm fine with back-porting to 3.4. As a heads up, though, anyone upgrading from 3.4.3 to 3.5 will have to remove the aged money changes from the 3.5.0 upgrade script. This kind of thing happens sometimes, of course. As long as it's clearly marked in the SQL, it should be simple to comment it out.

Alternatively, if we cut 3.4.3 today-ish, then we could build the 3.5.0 SQL upgrade atop 3.4.3, allowing us to remove the aged money changes from the 3.5 SQL upgrade.

Preferences? I'm fine delaying 3.5 to get this fixed as long as we maintain momentum.