In the past year we shipped what could be considered the final release for MCE Table Buttons (see 3.3.1). Given that this plugin only operates within the Classic Editor, that the Classic Editor is set for discontinued support at the end of this year (after being postponed from the end of last year), and that generally our plugins support WordPress minimum usually around 5.2 or above, I'm recommending that we consider archiving this project. That would effectively mean merging this PR, archiving the GitHub repo, pinning a message in the WP.org support forum noting the plugin has been archived/closed, and then closing/archiving the plugin on WP.org.
Alternate Designs
Keep the plugin on stable support and continue to test with major WordPress releases and bumping the "tested up to" value, but generally not performing any other work on the plugin (unless there's a reported security issue or other significantly worthwhile PR contribution).
Possible Drawbacks
700,819 all-time downloads and 60,000+ active installs would effectively lose on-going plugin support and maintenance.
Verification Process
This PR is but a simple README.md change, the larger work comes once this is approved/merged.
Description of the Change
In the past year we shipped what could be considered the final release for MCE Table Buttons (see 3.3.1). Given that this plugin only operates within the Classic Editor, that the Classic Editor is set for discontinued support at the end of this year (after being postponed from the end of last year), and that generally our plugins support WordPress minimum usually around 5.2 or above, I'm recommending that we consider archiving this project. That would effectively mean merging this PR, archiving the GitHub repo, pinning a message in the WP.org support forum noting the plugin has been archived/closed, and then closing/archiving the plugin on WP.org.
Alternate Designs
Keep the plugin on
stablesupport and continue to test with major WordPress releases and bumping the "tested up to" value, but generally not performing any other work on the plugin (unless there's a reported security issue or other significantly worthwhile PR contribution).Possible Drawbacks
700,819 all-time downloads and 60,000+ active installs would effectively lose on-going plugin support and maintenance.
Verification Process
This PR is but a simple README.md change, the larger work comes once this is approved/merged.
Checklist:
Changelog Entry
Credits
Props @jeffpaul.