I agree with both #3 and #4, its a question of whats the best compromise, whether its too late in the release cycle, and if not, what is the procedure to do fast track in a key change in a controlled and successful way.
This issue is obviously much more important for the server edition.
As regards #1, its unclear to me how to assign this bug to a specific release or package.
I agree with both #3 and #4, its a question of whats the best compromise, whether its too late in the release cycle, and if not, what is the procedure to do fast track in a key change in a controlled and successful way.
This issue is obviously much more important for the server edition.
As regards #1, its unclear to me how to assign this bug to a specific release or package.