ga_tokenizer - commit not showing up to 6.x-1.x-dev gz/zip

LOL! Funny, after waiting patiently for what felt like an eternity the download links are now working. However, my 6.x dev branch still doesn't reflect the latest code. Like I said in the original post, it typically goes into effect in near real-time. Any thoughts? I noticed in my Create Release page, it is strangely showing me a 6.x-1.x (6.x-1.x-dev) release to add to my project page. I generally don't see this when updating the release master. Also, if I try to select it, it gives me a scary red message:

The version you have selected (6.x-1.x-dev) is already in use by another release.
You can try again.

Are you sure you want to mark this release as a Security update?
If you select Security update, your release will not be published without the manual intervention of the Drupal Security Team. You should have already contacted the Security Team to coordinate a security advisory (SA) for your release before you committed any security-related patches.

I am still having issues rolling out a new -dev version. It's been 5 days and the -dev version advertised for the 6.x brach is still not updated. This is going to be an issue as I am rolling out another complementing module that needs what this module offers. I need these change to be in dev until I am comfortable with it.

The message about "The version you have selected (6.x-1.x-dev) is already in use by another release." won't let me submit that detected release (no button is available to submit), so my hands are tied at this point.

Peace,
Brian

Note: The commit that should have triggered the update of 6.x-dev was this one:
http://drupalcode.org/project/ga_tokenizer.git/commit/cd350c0

It seemed to have triggered something, the creation of a new branch in the Release Administration screen that I cannot choose because that release name already exists.