In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
(Ben Bucksch) wrote:
> IMO, the current situation doesn't help anybody.
Compared to withdrawing nightlies, the current situation is better for
people who in your categorization are considered "testers" and people
who have about the same skill level as "testers" but for some reason
don't use Bugzilla actively.
> * Builds targetted at developers
For some people (like me) they are better than no builds.
> * Useless (for them) website
There are a lot of issues wrt. the site including:
* The discoverability of documentation for developers could be better
* A FAQ for Web authors is needed (There already is a Bugzilla
component for Web author docs.)
* A FAQ for end users is needed (There's a Bugzilla component for end
user docs, too!)
* Pages on www.mozilla.org aren't W3C-compliant, which is kind of
embarassing
> I think, in this case, a social solution works best - just discourage
> users from using Mozilla, and they won't end up at our newsgroups or
> in bugzilla. (Unless they think Mozilla = Netscape, of course.) Clueful
> users that also care will end up at mozilla.org anyway (at least,
> because I redirect them there).
How do you suggest the discouraging to be carried out in a manner that
doesn't discourage clueful users who are potential contributors? You are
probably only redirecting users of Beonex. Beonex is available on
Windows and Linux which are already the top two Mozilla platforms.
There's a risk of making potential Mac or BeOS developers turn away.
> Why does the tarball then contain 3 MB of test binaries?
I have been told the QA needs them. However, the tests seem to be quite
static, so it would make sense to put them in a separate package instead
of transferring the same files with every nightly build.
> Why is the "homepage" of mozilla0.6 the same as the release notes?
In order to minimize the number of people who download the milestone but
don't read the relnotes (I think).
> > For example,
> > localizations are inherently for end users and not for developers.
>
> No, localizations are code, just like any other code is. They are not
> more or less for developer or user then the rest of Mozilla is.
A developer can't use a localization for dogfood with his/her latest
Mozilla build, because localizations aren't updated daily.
--
Henri Sivonen
[EMAIL PROTECTED]
http://www.clinet.fi/~henris/
