[wp-meta] [Making WordPress.org] #3428: Plugin Directory: enforce change levels - major, minor, fix

Making WordPress.org noreply at wordpress.org
Wed Feb 7 06:05:17 UTC 2018

#3428: Plugin Directory: enforce change levels - major, minor, fix
 Reporter:  galbaras          |      Owner:
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
 Plugin developers seem to have their own ideas of numbering releases and
 often introduce functionality changes into mostly-bug-fixing ones. This
 makes it harder to judge whether an update should be applied or bypassed.

 '''N.0.0''' should be used for major releases or significant code
 overhauls. Specifically, this should apply to anything requiring other
 components (themes, addon plugins) to be adjusted.

 '''N.M.0''' should be used for minor changes to the way the plugin
 functions. This can be the addition of actions and filters, changes to
 plugin admin screens and functional additions that do not change anything
 already being used.

 '''N.M.X''' should be used for bug fixes and security updates only. It
 should be a no-brainer to apply them, because they are most likely to make
 things better without breaking anything.

 It's unlikely that the plugin directory can prevent developers from doing
 the wrong thing, but it should at least guide them, and perhaps require an
 x.y.z version format and automatically label that version as a major,
 minor or fix to guide users as well.

 I've never submitted a plugin, so this clearly needs clarification, but as
 someone who manages WordPress websites, a good version scheme will help me
 a great deal. It should also help plugin developers streamline their

Ticket URL: <https://meta.trac.wordpress.org/ticket/3428>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list