Available Updates says new 6.x-2.x-dev is available as of March 19th after download still reported as 6.x-2.x-dev (2011-Dec-02)

> The March 19th commit to 6.x had to do with translation and wouldn't address any of your issues.

Yet, after another check of my "Available Updates" page and a subsequent download, unpack, upload, check updates cycle with the March 19th commit my updates page still tells me that I'm using the Dec 2nd commit, not the March 19th commit which I've gone through the motions of installing about 5 times now.

If this thread is listed as a "Sync or Update Issue" how do you figure it's "fixed"?

Sorry Bro, what the hell are you talking about?

I have deleted my local and the server copies of both the March 19th -dev tarball and its unpacked directory and contents, I've downloaded the March 19th -dev commit and unpacked it before uploading the taxonomy_menu directory and contents to ./sites/all/modules on the server, where I have indeed then run ./update.php . . .
. . .all several times now!

When I go to my site's "Available Updates" page and click to run /admin/reports/updates/check, Taxonomy menu is still listed as being at the Dec 2nd -dev commit with the March 19th showing as an available update. . . EVEN THOUGH I HAVE GONE THROUGH THE PROCESS OF UPLOADING THE NEW CODE AND UPDATING SEVERAL TIMES!

The reason I'm banging on about this is that Taxonomy Menu is the single module which is preventing me from launching this site.
And I'm trying to work out why! Part of that process for simpletons like myself is to check if I'm running a current release of the module. Your module is reporting its own installed and activated version incorrectly. I'm trying to alert you to that fact but you seem to be mostly concerned with blowing me off which makes me think. . .

Your module provides EXACTLY what I'm looking for, it generates the link text and urls perfectly, but it breaks a short way into generating the menu for which I need it! (I'm expecting it to generate about 200 nested menu links to be displayed as a jquery menu but Taxonomy Menu ceases to function at somewhere between 50 and 90 menu items.)

The point being that your module DOES NOT WORK in my real world context. And in my ever-less-than-humble-opinion that should be something that concerns you as the maintainer of the module but you seem to be mostly concerned with dismissing issues with the least amount of effort and thought possible.

I'm not talking about it theoretically working on a developers platform under pristine lab conditions, cooled by propeller driven baseball caps.

I'm talking about a site which runs many other key, heavy-lifting Drupal modules (including Devel) flawlessly BUT taxonomy_menu DOES NOT RUN FLAWLESSLY. I can only assume that there is an issue with Taxonomy Menu or it conflicts with another module both of which should concern you. . . no?

Am I making sense yet?

Oh and BTW, you're March 19th -dev commit isn't reporting itself correctly on /admin/reports/updates
and guess what, I just installed / enabled the March 19th -dev commit on another drupal site and it still reports its installed version as the Dec 2nd commit with the March 19th as an available update.

Am I making sense yet?