I know it looks confusing, but 0.23 and 0.24 get separate bug tasks here because they got different fixes for this bug. The fix landed on 0.24 series after we had branched 0.23. So the two fixes have different histories and need to be tracked separately.
I know it looks confusing, but 0.23 and 0.24 get separate bug tasks here because they got different fixes for this bug. The fix landed on 0.24 series after we had branched 0.23. So the two fixes have different histories and need to be tracked separately.