Since 99% of Evergreen libraries are hopefully already on a release that is later to 2.5, should this bug still be open? I expect most libraries that were using floating in their copy templates prior to 2.5 have dealt with this issue in one way or another.
Since 99% of Evergreen libraries are hopefully already on a release that is later to 2.5, should this bug still be open? I expect most libraries that were using floating in their copy templates prior to 2.5 have dealt with this issue in one way or another.