To create the 4.3.0.Final release we're branching off from the very
stable 4.3.0.CR1 tag and applying a subset of the patches we applied
to master since them, as some are more appropriate for the next
iteration 4.4.
I'll push the produced branch as "4.3" and mvn release:prepare is
going to set the next version for this branch as 4.3.1-SNAPSHOT
(however there is no expectation for an actual 4.3.1 release).
I don't think this affects any ongoing work, just don't be too
surprised if you won't see the 4.3.0.Final among the ancestors of 4.4
work in your git logs.
Sanne