FPWD → CRS transition has onerous change documentation requirements

[dontcallmedom]

For the first transition to CR, the transition requirements include:

• documenting all classes 4 changes (new features)
• documenting all classes 3 changes (substantive changes)
• optionally documenting all other changes

While this feels meaningful for transitions post 1st-CR, it feels onerous and not very meaningful for the first CR transition, since in most cases one would expect a lot of such changes between FPWD and CRS (unless "since previous publication" is meant literally as since the previous WD rather than what I think is meant as "since previous transition" - but then that would be meaningless, esp in a world of automatic publications).

[frivoal]

I think you're right that this should indeed be improved, but I don't think this is blocking/urgent, because indeed, the literal interpretation is that you have to document those things since the last publication, not since the last maturity change. And so it doesn't currently require (and wasn't intended to require) documentation of everything that has ever happened since FPWD. We should probably make it clear enough to require documenting everything since the previous CR(S), but be more nuanced for the pre-CR phase.

[dontcallmedom]

(I agree this is not on the critical path for Process 2023 - I was reporting the issue now since it was fresh on my mind from a recent transition request)