Note that 2.4.8 would be the version that had the bug (if it was released), so the fix only needs to go in there so that if we *do* release 2.4.8 we don't have the bug.
Note that 2.4.8 would be the version that had the bug (if it was released), so the fix only needs to go in there so that if we *do* release 2.4.8 we don't have the bug.