Henri Sivonen wrote:

> Compared to withdrawing nightlies

No, only the milestones. I know that the nightlies are very important 
for testing.

>>           * Builds targetted at developers
> 
> For some people (like me) they are better than no builds.

I count you as "developer". :)

> (There's a Bugzilla component for end user docs, too!)

End user docs are IMO part of the app and needed by distributors just as 
source code is.

>> 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?

With the website, by explaining for who mozilla.org provides services 
and for who not. Keywords like "bleeding egde" (-> stay here) vs. 
"stability" (-> go to distributor) come to my mind.

Say, we had no milestone binaries and would keep the scary warnings 
about nightlies*

*BTW: Being back to the trunk, I cannot second the general notion that 
it were better than Mozilla 0.6. The trunk has various problems, which 
might be minor for us (workaround exists), but cause a truckload of 
complaints by end-users. E.g.
- the drop-down of the addressing widget *always* shows "To:"
- the prefs pane is just as small so that you don't see the "Apply" 
button, but it looks OK otherwise.
(I bet I could go on with 5 more such problems)
If I compare the sometimes hostile reactions of a few Beonex users to a 
bug, which in some cases deliberately changes the Windows filetype 
associations to Beonex, I can guess, what would happen, if I released a 
trunk-based binary. So, Asa, if you read that, please plan a 
stabilisation period before 0.8, if you release that.

> You are 
> probably only redirecting users of Beonex.
> There's a risk of making potential Mac or BeOS developers turn away.

I do plan binaries on Mac and BeOS. If I could, I would make them today.

>> Why does the tarball then contain 3 MB of test binaries?
> 
> I have been told the QA needs them.

Right. But end-users have no use for them.

>> 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).

Yes, but normal users need to know first, *what* that *is*, before they 
read about the problems, not?

>> 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.
> 
I think, de-AT is, but I don't know for sure. Anyways, I meant 
s/developer/distributor/.


Reply via email to