[wp-meta] [Making WordPress.org] #8163: Versions are not available for download

[Making WordPress.org]

#8163: Versions are not available for download
------------------------------+----------------------
 Reporter:  themetechmount    |       Owner:  (none)
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------
Changes (by dd32):

 * priority:  high => normal
 * resolution:   => invalid
 * status:  new => closed
 * component:  Version Control => Plugin Directory


Comment:

 Hi @themetechmount,

 For WordPress.org/plugins issues, the best contact is to contact the
 plugins team at plugins at wordpress.org.

 At the top of https://wordpress.org/plugins/truebooker-appointment-
 booking/ this message is visible:

 >  During the last import of your plugin the following warnings were
 encountered. This message is visible only to the plugin authors &
 committers.
 >  The Stable Tag field is invalid, the specified SVN tag /tags/1.1.3/
 does not exist. /trunk/ will be used instead.

 Looking at https://plugins.trac.wordpress.org/browser/truebooker-
 appointment-booking/#tags/ it appears that you're:
  - Committing tags inconsistently, using `tags/1.0.9` and `tags/V1.0.8`
  - Relying upon `/trunk/` packaging, as you're not creating `tags/1.1.3`
 when you release a new version (AS specified in your trunk/readme.txt's
 "Stable Tag:" field)
  - Committing a ZIP file to the SVN tag, whereas you should be committing
 code, and letting us generate the ZIP file.
  - Even when you've added files, such as in `tags/V1.0.6` you've also
 added the ZIP.
  - Please use `svn copy` to generate tags from trunk.
  - Please consider looking at the SVN for other plugins through the above
 trac instance, to see how they manage their SVN repo.

 Please read https://developer.wordpress.org/plugins/wordpress-org/how-to-
 use-subversion/ for further information on using SVN. If you don't like
 using SVN, and use GitHub or another tool, there's often 3rd-party plugin
 deployment tools available (I can't suggest any specific one).

 I'm closing this ticket as `invalid` as there doesn't appear to be a bug
 on WordPress.org specifically, just a misunderstanding of how to use our
 tooling. You're not the first person to run into this kind of thing, and
 I'll follow up with the plugins team to see if they think we have any
 lacking documentation.

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