MySQL Bugs: #58077: 5.5 download have gone!

Bug #58077	5.5 download have gone!
Submitted:	9 Nov 2010 10:35	Modified:	9 Nov 2010 22:04
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Websites	Severity:	S2 (Serious)
Version:	5.5	OS:	Any
Assigned to:	Markus Popp	CPU Architecture:	Any
Tags:	qc

Description:
The page http://dev.mysql.com/downloads/mirror.php?id=386673#mirrors has issues

1) It points to 5.5.3.  Where did 5.5.5 and 5.5.6 go?
2) the combo box where to select mirrors is not functional (in any browser)
3) Mirrors such as ftp://mirrors.dotsrc.org/mysql/Downloads/MySQL-5.5/ are empty (even 5.5.3 is not there any more)

How to repeat:
See above.

Suggested fix:
I cannot know if this is a website issue only (due to restoring an old backup for instance) or if it represents some change of policy. In that case some announcement would be appropriate.

Weird, indeed...

Seems like mirrors have started populating with 5.5.7.  But website still links to 5.5.3-m3.

Still no 5.5 Windows binaries for download!

Is this issue still up-to-date? I'm seeing 5.5.7-rc when I go to http://dev.mysql.com/downloads/mysql/5.5.html

Please note that linking to a specific ID (like 386673 in http://dev.mysql.com/downloads/mirror.php?id=386673) will always point you to this specific download, which may not be the current one anymore, as new versions are released.

To get the current links, always go to http://dev.mysql.com/downloads/mysql/5.5.html - here is where the links go to the current version, with different file IDs.

It seems to be OK now.  All downloads I can identify are there, as well as website is functional. I am downloading 64 bit Windows server.

But something went terrible wrong this time when you decided to release 5.5.7.  Looks like you did things in the wrong order (deleted the old ones before the new were available) and the web page was (at least) a 4-6 month old version pointing for 12 hours to non-existing and outdated binaries (5.5.3 m3).

I have a clue how this may have happened. I will follow up on that and try to make sure this doesn't happen again.

As this particular bug is resolved, I'm going to close the bug report. Thank you very much for reporting!