[wp-meta] [Making WordPress.org] #5645: Feature Request: Update on reversion to `trunk/`

[Making WordPress.org]

#5645: Feature Request: Update on reversion to `trunk/`
------------------------------+---------------------
 Reporter:  rumperuu          |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by Ipstenu):

 Word of warning: If you sync ''every'' commit from Git to SVN, you'll
 eventually get a stern email from the plugins team asking you to stop,
 because (in the past) we used to regenerate all your zips when you did
 that. Now we only rezip the one branch you're on (say, Trunk) but still,
 there's no reason to do that.

 > I didn't expect the versioning info in readme.txt to have any effect,
 just as the version number in the Plugin base file docblock doesn't

 This is actually documented. https://developer.wordpress.org/plugins
 /wordpress-org/how-your-readme-txt-works/#how-the-readme-is-parsed

 If there's no tag, it reverts to trunk.

 Also if you change the version in the plugin base but not the readme, you
 could cause your plugin to act 'out of date' and constantly try to update.

 tl;dr? Readme and main plugin file ''must match'' if you want things to
 work as expected.

 > The ‘Previous Version’ selector lists the version in trunk/ as the
 ‘Development Version’, which as I just found out is not necessarily the
 case depending on what you put in trunk/readme.txt.

 No, trunk is ''always'' your dev version. Even if you don't use it like
 that, that's the system setting. Always has been.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5645#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org