Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.
I guess this is where my mindset is different... I saw the two surveys we ran as beta testing.
It still feels anything but stable to me and given the lingering bugs around ease of use, T119367, T115485.
That said I guess we can aim for a 2.0.0 release for those.
If the main motivation is we've already run surveys in production, to avoid confusion it feels like we should just reset the version number and do a release afterwards with the minor changes (it's already confused @Florian)
Up to you guys what you want to do here, don't feel strongly either way.
We couldn't do the 1.0.0 blank release due to a couple cherry-picked commits. Instead, I've changed the next release to 1.1.0 and clarified in the commit message why. The only thing I'm uncertain of is if I should rename 0.6.0 to 1.0.0 in the HISTORY file -- since that's effectively what we wanted to do -- or if I should leave it since nobody would be able to find a "Release 1.0.0" commit.