Yeah, there are issues with the caching. Email plugins@wordpress.org if it doesn’t resolve itself in a day.
This is still broken, and an email to plugins@wordpress.org on the 19th of april was not effective.
It looks like while the date is wrong, everything’s being updated.
In SVN trunk readme.txt I see Stable tag: 0.1100509
Reviewing the DIFF log it has all but the last change: http://plugins.trac.wordpress.org/changeset?reponame=&new=382991%40latest-twitter-sidebar-widget&old=382665%40latest-twitter-sidebar-widget
By the way, you’re not tagging your versions, so people can’t easily go in and download them 🙂
Read http://wordpress.org/extend/plugins/about/svn/ and look at Task #3 🙂
Yes, everything is working fine except that date on the page.
I am a bit confused by your comment, “so people can’t easily go in and download them.” My users are getting the latest update with the notification inside their WP dashboards without issue, and clicking the download link on the plugins page is always returning the last version I have committed.
The page you linked says, “This lets your users easily grab the latest (or an older) version, it lets you keep track of changes more easily, and lets the WordPress.org Plugin Directory know what version of your plugin it should tell people to download.” I’m not sure how these things are not sufficiently happening now with the exception of “(or an older) version.” Perhaps older versions would be nice to access if my plugins were much larger projects.
Older versions are nice because if you push out an update that breaks my site, I can go, grab the old version, and restore.
Example.
http://plugins.svn.wordpress.org/ban-hammer/tags/ has all the tags of all my versions.
http://wordpress.org/extend/plugins/ban-hammer/download/ lists ALL my versions, from 0.1 to development, so someone can gab whatever they want.
It’s not REQUIRED, it’s just good practice.