11.2.x is released - update NEXT_MINOR

Changing the script constant from 11.2.x to const NEXT_MINOR_DEV = '11.3.x'; is enough to make 'check versions' pass. But this will not actually change any core versions being tested against.

CORE_NEXT_MINOR is still set to 11.x-dev. The description of this variable is
"Once the current minor-dev branch enters a beta phase, this is the dev branch for the *next* minor version."
The script allows this to be changed now to 11.2.x - I cannot see any prompt in the script that would alert us to changing this when we get to 'beta'. Is that something to add in?

Yeah, once it's in beta phase, we should update to this CORE_NEXT_MINOR: 11.2.x-dev. Maybe we can do something in the script to check when 11.2.0-beta* is available.

Maybe we can do something in the script to check when 11.2.0-beta* is available.

Yes we can. You can merge this MR, but leave the issue open, as the background info is here.

Great. I'll do that then, so we can also rebase the other open MRs.