[wp-meta] [Making WordPress.org] #6380: Prevent use of 'trunk' as a Stable Version

Making WordPress.org noreply at wordpress.org
Mon Jun 27 20:31:30 UTC 2022

#6380: Prevent use of 'trunk' as a Stable Version
 Reporter:  Ipstenu           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
 In order to make rollbacks more stable, and reduce friction with users,
 the time has come.... to chop down trunk.


 Currently if you use {{{Stable tag: trunk}}} in your readme, it will pull
 the files from trunk. And that's great, but it can cause issues with
 figuring out what the rollback should be.

 It shouldn't be bad with our proposed changes, but it does mean that when
 we want to expand and say "rollback 2 versions" (or even to a specific
 version), if everything's always in trunk and never tags... can't download
 the old version :(

 Trunk as 'stable' is meeting the end of it's life.

 The 'best' path might be to check the readme.txt for a stable tag value
 and, if it's trunk, error back "Stable Tag cannot be trunk. It must match
 the Version as indicated in your plugin headers." Bonus, make sure we only
 check for the FIRST iteration (some people re-used Stable Tag per version
 in their changelogs).

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

More information about the wp-meta mailing list