[wp-meta] [Making WordPress.org] #6325: Can you add next all latest version on dropdown?
Making WordPress.org
noreply at wordpress.org
Thu May 26 02:17:30 UTC 2022
#6325: Can you add next all latest version on dropdown?
-----------------------------+----------------------
Reporter: sumitsingh | Owner: (none)
Type: defect (bug) | Status: closed
Priority: high | Milestone:
Component: Trac | Resolution: invalid
Keywords: has-screenshots |
-----------------------------+----------------------
Changes (by dd32):
* status: new => closed
* resolution: => invalid
Comment:
This is working as intended.
The `Version` field references the first version of WordPress that a bug
affects.
Due to a number of reporters changing the version to a later version (ie.
6.0) when a new version was released, we've removed the ability for non-
trac-gardeners from setting the Version field to a newer version than it
currently lists.
The fact it lists 5.7.1 & 5.7.2 is a little bit of a bug, but not one that
we cared enough about fixing.
Additionally, we don't add security releases / maintenance releases to the
list once the version is no longer the stable release, unless required.
That's why it tops out at 5.7.2 rather than at 5.7.6.
If a tickets version needs to change to a later version, as the one
specified is incorrect, comment on the ticket with the reasoning, and a
bug gardener can update it.
If a bug is introduced into a security release and a version field needs
adding for a non-stable release, we'll do that at that time.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/6325#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list