[wp-meta] [Making WordPress.org] #4380: Plugin Directory: Be more flexible with the detected current major WP version
Making WordPress.org
noreply at wordpress.org
Wed Apr 10 21:02:53 UTC 2019
#4380: Plugin Directory: Be more flexible with the detected current major WP
version
------------------------------+---------------------
Reporter: Ipstenu | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone:
Component: Plugin Directory | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by SergeyBiryukov):
Replying to [ticket:4380 Ipstenu]:
> The problem here is that value is checked when seeing if a plugin is
tested up to the current stable version, and some developers want to
update their code once they've tested against Beta releases. This is a
good practice, and should be encouraged, however as it stands today, their
plugins will throw an error if the version is higher.
Related: [7874], #3936.
> This should be changed to factor in a +1 version or to allow for RCs...
I haven't tested yet, but looking at the `(float)$version >
(float)WP_CORE_STABLE_BRANCH+0.1` condition, that seems to be the case.
Does `Tested up to: 5.2` currently cause a warning? Is it a warning in the
readme validator, or the "has not been tested with the latest 3 major
releases" plugin banner?
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/4380#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list