Comment 1 for bug 140049

On Mon, Sep 17, 2007 at 05:10:27AM -0000, Scott Ritchie wrote:
> The current way of "warning" the tester that it is oversized is to
> create a file amidst the huge list of useless file ending in .OVERSIZED.
> It is very easy to ignore this file, or even to see it and not know what
> it means, since it's next to a bunch of other things you will not even
> want to click on.

You may not have a need for them, but the other files there are far from
useless. Developers do use them, and regularly.

Most of the other files in that directory have corresponding text which
describes what they do. This would be useful for .OVERSIZED as well.

> I think the simplest way to avoid this is to just put a warning up at the top of the automatically generated download page in big letters. Something like "Warning: This image is oversized and will not fit onto a standard CDR. You may still use it to test burning to a virtual machine or DVDR, however."

This is not straightforward to do, since the HTML is static (it's identical
for every build). I'm not sure that it's worthwhile, as there are a lot of
other ways in which a daily build can be faulty, because they are
automatically generated and not tested before release. If you need a
development build which is known to work, our recommendation is to use a
milestone build (such as Tribe 5).

--
 - mdz