On Jan 19, 2010, at 1:48 PM, William Bauer wrote: > This is minor compared to all the problems being posted about v130 (which I > stopped using because it was so frustrating). But here goes: > > What's the process for reporting errors on the downloads page below?
Send an email to me or this mail alias. > I'm hoping this forum is the answer. For example, FF 3.6rc2 is available if > you change "rc1" to "rc2" in the download link, but the web page doesn't > reflect this. I changed the download link for 3.6rc2 about 24 hours ago. You should see 3.6rc2 links if you refresh the page. The process is like following: 1) I built Firefox / Thunderbird, and upload them to release candidates directory of ftp. 2) Mozilla.org RE sync the files to releases.mozilla.org. 3) If I found Mozilla.org RE didn't sync the files of Solaris, I will do it. 4) Mozilla.org add entries to their server, so the download links will work. 5) I check the download link, if it's not working, I file a bug in bugzilla and wait Mozilla.org RE to fix it. 6) I update the wiki page of opensolaris.org Since there's time difference between Mozilla.org RE and me, it could cost 24hrs or even longer for each step. Feel free to ask me if you found any problem. Honestly, I don't have time verify every link, I just do a random check. > The Seamonkey 2 link hasn't worked for some time and is way out of date (no > longer in beta). OK, you just found a broken link. Seamonkey builds are not built by me. Unless somebody build them and upload them to somewhere, I can't help. > I greatly appreciate that these downloads are available and kept current > within a day or two of release, and usually the FF and TB links are changed > fairly quickly--just not this time! Thanks. Ginn > > http://hub.opensolaris.org/bin/view/Community+Group+desktop/development > -- > This message posted from opensolaris.org > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org
