We've run into an issue where an API change was introduced into the 1.0.5 builds which is going to require that we replace 1.0.5 with a new release. Please hold off on doing any further localizations until we have the new release ready to go. If all goes well, this should be on Monday.
> We've run into an issue where an API change was introduced into the > 1.0.5 builds which is going to require that we replace 1.0.5 with a new > release.
Is this also the reason why the Firefox 1.0.5 localized builds aren't released yet?
> We've run into an issue where an API change was introduced into the > 1.0.5 builds which is going to require that we replace 1.0.5 with a new > release. Please hold off on doing any further localizations until we > have the new release ready to go. If all goes well, this should be on > Monday.
Nice joke... again. Especially for all our users which waiting for a new localised version of Mozilla Thunderbird. Mozilla Firefox 1.0.5... same problem? No new informations here.
This looks like that Mozilla Foundation has new motto: "We will hide problems"
Pavel Cvrcek wrote: > Nice joke... again. Especially for all our users which waiting for a new > localised version of Mozilla Thunderbird. Mozilla Firefox 1.0.5... same > problem? No new informations here.
I don't quite see what the problem is. What more information is necessary? Asa posted that message to save all the localisers from doing a load of unnecessary work. Why is this bad?
> I don't quite see what the problem is. What more information is > necessary? Asa posted that message to save all the localisers from doing > a load of unnecessary work. Why is this bad?
The problem isn't about the fact that he posted the information.
The problem is we (the l10n teams) are getting no real information from you (you=Mozilla.org) about what's happening. "Something's wrong, don't localize". OK. But the people are asking us, the l10n teams about why there are no localized versions. And when we say to those people "Mozilla.org has some problems" it's a silly response, because it's not a response at all.
What more information is necessary? See my post below. Or read bug 300028 comments from 33 to the end.
> I don't quite see what the problem is. What more information is > necessary? Asa posted that message to save all the localisers from doing > a load of unnecessary work. Why is this bad?
There is no oficial information for users yet! Why? Users are downloading bad release and they don't know that something is wrong. Why do you hide problems?
L10n teams haven't got enough information about situation (now it's better then yesterday but...) and they don't know what say users, press etc. I read some bad articles in on-line magazines yesterday. This isn't good for propagation of FF and THB.
First off you guys are mozilla.org there's no us and them. We are all in this together. Some more information:
* We are looking at doing a Firefox 1.0.6 and Thunderbird 1.0.6 * There were some API changes that affected distributors and extension developers. * This release will address those changes.
Information about the Firefox 1.0.6 and Thunderbird 1.0.6 builds will be up there.
Also, we're looking into the issue of simultaneous release. We did that for Firefox 1.0, we haven't done simultaneous releases since then (because it's hard to do!). We'll revisit the issue considering 1.0.5 and also how we can do better with Firefox 1.1.
Pavel Cvrcek wrote: > Asa Dotzler napsal(a): >> We've run into an issue where an API change was introduced into the >> 1.0.5 builds which is going to require that we replace 1.0.5 with a >> new release. Please hold off on doing any further localizations until >> we have the new release ready to go. If all goes well, this should be >> on Monday.
> Nice joke... again. Especially for all our users which waiting for a > new localised version of Mozilla Thunderbird. Mozilla Firefox 1.0.5... > same problem? No new informations here.
> This looks like that Mozilla Foundation has new motto: > "We will hide problems"
> First off you guys are mozilla.org there's no us and them. We are all > in this together. Some more information:
> * We are looking at doing a Firefox 1.0.6 and Thunderbird 1.0.6 > * There were some API changes that affected distributors and > extension developers. > * This release will address those changes. > Please check the Mozilla QA blog as we'll post more information there as > they come available. > http://weblogs.mozillazine.org/qa/
> Information about the Firefox 1.0.6 and Thunderbird 1.0.6 builds will be > up there.
> Also, we're looking into the issue of simultaneous release. We did that > for Firefox 1.0, we haven't done simultaneous releases since then > (because it's hard to do!). We'll revisit the issue considering 1.0.5 > and also how we can do better with Firefox 1.1. > -Rafael
Rafael, why don't you send to Mozilla Europe's internal list a message when you run into problems such as this one or simply when you make a release ?
So as to know when I have to update our pages I have to watch changes on ftp servers and spy on all mozilla blogs often during the night because of the hour difference between the US and Europe, not really convenient.
It would spare us a lot of time and frustration if you could just send a message to one of our internal lists when there are releases and/or problems with releases.
> First off you guys are mozilla.org there's no us and them. We are all > in this together. Some more information:
> * We are looking at doing a Firefox 1.0.6 and Thunderbird 1.0.6 > * There were some API changes that affected distributors and > extension developers. > * This release will address those changes.
Thanks. Better late than never. Please next give enough oficial information in time. We can publish it on our local website and say it to users, press etc.
> there's no us and them
Maybe but one thing is what MoFo says and second, what MoFo does. Very demotivative for us.
On 2005-07-17, Gervase Markham <g...@mozilla.org> wrote:
> Pavel Cvrcek wrote: >> Look like bad days for Mozilla....
> Well, of course it's not a good day. We messed up a release :-(
That, as I see it, was the first problem. The other problem was the confused communication - security advisories were published with references to releases that didn't exist at the time of publication and then rather than announcing the problem when the decision to cancel the Suite and localised releases was made, bits of information appeared in various places over the course of a couple of days.
> First off you guys are mozilla.org there's no us and them. We are all > in this together. Some more information:
Glad to hear this... but I can't resist noting that it would also be nice to be part of the need-to-know group in matters like these. (I'm assuming somebody was in the loop of knowing what's up with the release etc. which might not be true). Fortunately this mess up has happened during the summer, when few people care.
> ...
> Also, we're looking into the issue of simultaneous release. We did that > for Firefox 1.0, we haven't done simultaneous releases since then > (because it's hard to do!). We'll revisit the issue considering 1.0.5 > and also how we can do better with Firefox 1.1.
The impact of the current policy should indeed be re-evaluated. Even back here in Finland we've had on-line mags reporting separately on the English release (with a sombre note about no l10n version yet) and later on the Finnish version [1]. It's not likely that such generosity with reporting continues.
On the whole, the logic of treating non English speakers as second class users is not smart and just alienates these (i.e. the majority of) users. Personally, I can't understand why en-US users should get their updates sooner than ab-CD users,? ...given that the ab-CD localized version has been cleared by the locale owner in a reasonable time frame... say e.g. 24h or 48h from en-US sign off.
