[wp-hackers] plugin updates on wordpress.org

[Rich Pedley]

On 04/01/2011 08:50, Johan Eenfeldt wrote:
> On Wed, Dec 8, 2010 at 5:19 PM, Rich Pedley<elfin at elfden.co.uk>  wrote:
>> On 08/12/2010 15:59, Otto wrote:
>>>
>>> On Wed, Dec 8, 2010 at 9:32 AM, Rich Pedley<elfin at elfden.co.uk>    wrote:
>>>>
>>>> http://wordpress.org/extend/plugins/eshop/changelog/
>>>>
>>>> doesn't match either:
>>>> http://plugins.trac.wordpress.org/browser/eshop/trunk/readme.txt
>>>> or
>>>> http://plugins.trac.wordpress.org/browser/eshop/tags/6.0.2/readme.txt
>>>>
>>>> (specifically the small section about Version 6.0.2 in the Changelog).
>>>>
>>>> The download from the plugin page shows correctly as 6.0.2 and contains
>
>>>> the
>>>> upto date readme.
>>>>
>>>> is this an issue with my usage of SVN or an issue at WordPress.org ?
>>>
>>> The "plugin display" data doesn't update at the same time as the
>>> plugin zips get rebuilt and such. So it's highly likely that the
>>> downloads will appear before the new info appears in the Plugin
>>> display. This is a consequence of us using multiple servers. Only one
>>> server updates the plugin display, whereas they all update the zips
>>> for download.
>>>
>>> So sometimes, yes, the data shown will be old for a while. Generally,
>>> you just have to wait for it to happen. :)
>>
>> and as if my magic... it suddenly appears. I waited 2 days before reporting
>> it as well!
>>
>> Maybe someone could put together a wiki page explaining all the possible
>> delays when updating (or add it to the plugin developer page?) and how long
>> to wait before flagging it up.
>
> So how long should we wait to report it when plugin information
> doesn't get updated from the readme?
>
> This is the third day since tagging a new release (which got picked up
> immediately, thanks!) and changelog etc still shows the old
> information. Screenshots are from the new release, but descriptions
> are from the old one, which is kind of weird.
>
> Plugin: http://wordpress.org/extend/plugins/limit-login-attempts/

Believe me it isn't just you.

I have recently been informed that they do know about the issue and 
someone is working on it.

Rich