Update "beta" label for Aztec in app settings

[rachelmcr]

Under Me > App Settings we have an editor setting that still lists Aztec as the Beta editor.

Especially with Gutenberg coming out, we need to relabel Aztec so it's clear it is the latest stable editor, not beta. (Also, do we need to keep Aztec, Visual, and Legacy editors all available there?)

Note that this is not an issue in iOS, which no longer has an editor selector (only Aztec).

cc @hypest

[hypest]

Good point and question @rachelmcr , thanks for opening this ticket.

My suggestion would be to rename "Beta" to "Classic" to perhaps closer mirror the Classic editor on WordPress-web, and in preparation of discerning from "Gutenberg/Block" a bit later. We should probably do the rename asap so people can have some time to get used to the new name. cc @loremattei , @koke

In terms of keeping all past editors or dropping any, I think we were keeping Visual as it had better media performance in cases and we were also keeping Legacy for some reason. @daniloercoli , perhaps you have some recollection or insight about the Legacy editor?

[koke]

Classic makes the most sense. Still it's really confusing to face a choice between "Legacy", "Visual" and "Classic" if you don't know all the history 😞 Maybe we can call it "Default" so at least it's clear what's the recommended one?

Looking at the data we have I see less than 3% of posts used anything other than Aztec, so we might want to consider dropping the other two early.

[rachelmcr]

I agree that if we have all three it's confusing to choose between them. If we want to keep the reference to Classic perhaps Aztec could be labeled "Classic (Default)" or something like that.

[daniloercoli]

In terms of keeping all past editors or dropping any, I think we were keeping Visual as it had better media performance in cases and we were also keeping Legacy for some reason. @daniloercoli , perhaps you have some recollection or insight about the Legacy editor?

You're right about the Visual editor (the one powered by web-view). It's there to help users loading posts with a lot of media that fail in Aztec.

Looking at the data we have I see less than 3% of posts used anything other than Aztec, so we might want to consider dropping the other two early.

I vote to drop Legacy and Visual asap, and check the reviews/feedback/help requests from our users.

[hypest]

My pref as well would be to drop Legacy at least, check the usage stats about the Visual and drop it too if numbers are too low or not supportive for the case (i.e. used on non media heavy posts). Ending up with Classic + Block editor soon would be ideal for maintainability.

[SiobhyB]

+1 for removing Legacy and updating the Beta label. :D I just posted a case where Legacy caused some confusion for both a user and a HE in p4a5px-2jk-p2. Users are currently stuck in HTML mode if they're on the Legacy editor, which may be even more confusing when editing posts created in Gutenberg (due to the markup generated for blocks). Multiple editors can also cause unnecessary confusion from a support-perspective.

[koke]

The old editors were removed from the UI in #9208