Remove all code for the GWT editor
Ensure all editor links in Zanata open the correct editor
Ensure that bookmarked editor links open the editor
Links that were directly to the old editor may show an error page and link or redirect to the new editor. The link or redirect should open the correct workspace with the correct document and text flow selected
It seems like almost every issue listed as a blocker here should be part of the epic instead.
Are you disagreeing about what stage in the process we should switch the React editor to be the default?
There is https://zanata.atlassian.net/browse/ZNTA-851 which tracks all these less critical features to implement before removing the old editor entirely, but after making the new one the default. The current delineation was worked out with product owner and translation managers, but that was 16 months ago so the situation may have changed.
I forgot the rationale we were using back then, because I was surprised at just how many features we are treating as less critical. I suppose we could switch to React before it's a complete replacement for the GWT editor, at the cost of a downgrade in the users' experience.
But I don't think we should do so unless we have a pretty good idea that the missing features are in fact less important. We may need better analytics. Or perhaps might be able to work with some translators to get an idea which editor features they are really relying on these days.
Also, once we switch the default, we will need to maintain two editors at production level until the GWT editor is removed. If adding the remaining features is going to be a long process, that means a long time where we will have to maintain two editors at production level.