Sourceforge file release bugs.

I just finished uploading zinf 2.2.5 Fedora RPMs.  The zinf 2.2.5 release 
also includes RPMs for dependent libraries (gtkmm, metakit, et al).

In the process of doing that I came across some sourceforge bugs, that 
others should be aware of.

The RPMs for the dependent libraries were uploaded earlier, as part of the 
beta release, so I tried moving them from the zinf-beta package (which is 
now hidden) to the zinf beta.

If I change the release on these files to zinf-2.2.5, the files are no 
longer listed under the beta release.  But, they are also not listed on the 
download page for the zinf 2.2.5 release.

At first, I thought they disappeared in the never-never land.  But then I 
noticed that the files are listed on the file release admin page for the 
2.2.5 release.  They are listed on the file release admin page, but do not 
appear on the download page.

I figured out that if I don't do anything on the 2.2.5 release page, but 
merely push "Update/Refresh" for each file, the file will then appear on the 
download page.  Definitely a bug.

Also, a "zinf-2.2.5.tar.gz" file was initially uploaded for the beta 
package, and there's now a "zinf-2.2.5.tar.gz" uploaded in the zinf 2.2.5 
package.  I've hidden the beta package, but did not touch the actual file 
entry.  I suspect that if I tell sourceforge to drop the file from the beta 
release, it'll drop the new file instead.  I'll wait until 2.2.6 is 
released, before experimenting.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBALvHlx9p3GYHlUOIRAuRpAKCAOcY1Nccfi0hUR/P5Bf8M+3oP0ACbBZsQ
C5uv4NdaJT0f1Yyt9R/jQcA=
=MjiM
-----END PGP SIGNATURE-----