[wp-meta] [Making WordPress.org] #3010: Plugin Directory: Replace "This plugin hasn’t been updated in over 2 years" banner
Making WordPress.org
noreply at wordpress.org
Sun Oct 15 10:20:25 UTC 2017
#3010: Plugin Directory: Replace "This plugin hasn’t been updated in over 2 years"
banner
---------------------------------------+-----------------------------------
Reporter: SergeyBiryukov | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Plugin Directory
Component: Plugin Directory | v3.0
Keywords: has-patch has-screenshots | Resolution:
---------------------------------------+-----------------------------------
Comment (by ramiy):
Replying to [comment:11 Ipstenu]:
> We know. The thought is that if you're 3 major releases behind, there
have been a LOT of changes, more than just two years may indicate.
I can understand your thought but I'm not sure this is the right way. I
have over 30 plugins, many of them are simple oEmbed plugins, registering
different oEmbed providers. Or simple plugins that add a simple shortcode
or a metabox.
Those plugin can't really break the site, they are tested on clients
sites. Releasing an update for dozens of plugins every 3-4 months is not
realistic. At least not from a developer point of view.
Unless the repo can offer an easier way to update the `Tested up to`
value. In the past there was an attempt to give access to the plugin repo
back-end. It was supper easy to update the general setting of my plugins
using a meta-boxes. Not sure why it was removed.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3010#comment:12>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list