[wp-meta] [Making WordPress.org] #6957: Plugin Directory: Close plugins with no data
Making WordPress.org
noreply at wordpress.org
Fri Jun 9 01:17:24 UTC 2023
#6957: Plugin Directory: Close plugins with no data
------------------------------+---------------------
Reporter: Ipstenu | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone:
Component: Plugin Directory | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by dd32):
Replying to [comment:2 Ipstenu]:
> dd32 I think that check is wrong. I looked at flamix-bitrix24-and-
wpforms-integration and that's a real plugin with code.
Between `06/03/2023 05:25:19 PM` and `06/03/2023 05:30:20 PM` that was the
case as they `rm -rf`'d the lot:
https://plugins.trac.wordpress.org/changeset/2921053/flamix-bitrix24-and-
wpforms-integration
Sure, it was only 5 minutes, but I didn't at all intend on that list being
a "These plugins are ones that have no data" but rather "These plugins are
the ones we've processed this month which had no data when we looked at
some point".
> > Effectively, if trunk/ is empty, we treat it as having a readme.txt
that contains only Stable Tag: $highest_tagged_version.
>
> Yeah, we shouldn't do that. It makes it a metric pain to compare
changes. If people properly use trunk, then we can just use the change log
to know.
If they only use tags and never use trunk, it's actually easier, as you
can do `svn cp tags/1 tags/2; make-changes-to-tags/2; svn ci` which
results in a single commit, That's effectively how themes.svn works.
The Trac compare-changes functionality is often better than reviewing the
trunk changes alone too, as it's a combined diff rather than 10 individual
commits, I'll admit however, that Trac (well, SVN) gets it wrong sometimes
and thinks it's a 80MB diff when it's actually only 200K.
But I agree, we should ideally cease with that back-compat check here.
We'll need to figure out which plugins are relying upon it.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/6957#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list