[wp-trac] [WordPress Trac] #16522: WordPress repository not refreshing

WordPress Trac wp-trac at lists.automattic.com
Thu Feb 10 19:53:59 UTC 2011


#16522: WordPress repository not refreshing
----------------------------+-----------------------------
 Reporter:  fireproofsocks  |      Owner:
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  General         |    Version:
 Severity:  major           |   Keywords:  svn
----------------------------+-----------------------------
 Every time I submit a change to my plugin, it does not show up on my
 plugin's download page.  I've had to submit each new version multiple
 times before it finally gets picked up.  It's extremely frustrating.

 '''To Repeat:'''
 1. Commit changes to SVN trunk
 2. svn copy http://plugins.svn.wordpress.org/custom-content-type-
 manager/trunk/* http://plugins.svn.wordpress.org/custom-content-type-
 manager/tags/1.2.3

 '''Expected:'''
 New version shows up for download.

 '''Actual:'''
 Nothing happens.  Devs get pissed.

 If there's documentation about how this should be done EXACTLY, then it
 should be included on the http://wordpress.org/extend/plugins/about/ page.
 The page here: http://wordpress.org/extend/plugins/about/svn/ is very poor
 because it does not explain how you can actually use SVN while developing
 a plugin.  It's correct in theory, but in reality, you wouldn't have your
 tags and trunk directory sitting in your wp-content/plugins directory --
 it's worth pointing out how you might check out the contents of the trunk
 directly to your local plugin folder, e.g.

 {{{
 svn checkout http://plugins.svn.wordpress.org/custom-content-type-
 manager/trunk .
 }}}

 And it should be made crystal clear which readme.txt is being read to
 produce the download page, and it should be crystal clear how the version
 in the information head relates to the Stable Tag in the readme.txt file.
 There are several interrelated moving parts here, and frankly, even after
 messing around with this for hours, I have no clear understanding of how
 this actually works.  If it were me, I'd scrap this whole thing and use a
 "tags/stable" branch that will always contain the version of the plugin
 that's visible on the download page.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/16522>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list