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

[WordPress Trac]

#16522: WordPress repository not refreshing
--------------------------------+----------------------------
 Reporter:  fireproofsocks      |       Owner:
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  WordPress.org
Component:  WordPress.org site  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:                      |
--------------------------------+----------------------------

Comment (by Otto42):

 Replying to [comment:21 solarissmoke]:
 > People are doing this *because* the problems are happening, and because
 it was [http://core.trac.wordpress.org/ticket/15794#comment:6 suggested]
 that this is all that is required to sort it out. Not the other way round.

 Yes, well, now I'm telling you otherwise. Don't do that.

 The process runs when it runs and that's when it runs. Simple as that. It
 works by looking at the revision logs, and it then processes through those
 to put the changes into place, as needed.

 "Bumping" increases the number of revision logs, making it have to do more
 work, making it take longer, making it less likely that your change will
 get noticed anytime soon. In other words, it's actually counterproductive.

 Now, if your change got legitimately missed in some manner (still working
 out how that can happen), then bumping might get it to notice, but no
 amount of bumping will make it happen sooner. Quite the opposite in fact.

 > Could you please tell us what does work? When the plugin page does not
 correspond with the `stable` tag in readme.txt, how can it be refreshed?

 What does work: Make the tag, update the readme in trunk to point at that
 tag, then *wait*. And yes, it may be a while.

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