Andrea Pescetti wrote:
Marcus Lange wrote:

Hi Andrea,

Currently we get some reports about broken links where users get a 404 error message. But actually the link is not broken, the build is simply not existing.

Well, I would consider it a broken link, it's a link to something that
does not exist.

sorry no, my option is different. A non-existing link is not a broken link as it hasn't worked ever. To be broken means that under normal conditions (e.g., after a typo was fixed) it would be OK.

Yes, the non-exisitng link is offered. But this is the automatic way the download magic is working. We cannot produce exceptions for special builds because team A has approved it but team B not. IMHO there has to be a common basis.

And in my opinion it is to test and approve wJRE *and* nonJRE builds if they are available for the same platform (at the moment it's for Windows and Linux x86 RPM).

I can understand this workaround of asking N-L teams to approve all
builds, and surely it would be a way not to confuse users too much. But
I find the approach flawed: the only sustainable solution would be that
download.openoffice.org knows what builds are available. Technical
limitations of the download system should not turn into a burden for N-L
teams.

I don't know why it should be a burden to do one of the most importent thing in QA: testing and approving. ;-)

I think it shouldn't be terribly hard for MirrorBrain to produce a
snippet of JavaScript, to be updated at every mirror synchronization,
that would simply provide an array of available builds. The current
download pages could just embed it and modify their current behavior
based on that knowledge. Wouldn't this be a better solution?

Mirrorbrain cannot produce anything as it is "just" a redirect system.

And fixing the download system for every release is no solution. If there would be *at least* a fixed set of builds we could create it out of this. But at the moment it's not; at least not really complete.

Please believe me, sometimes it's really a pain to find a solution on the webpages for every new exception. ;-)

Best regards

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to