[POSTPONED] Firefox 3.6 -> 7.0.1 advertised update offer

[Christian Legnitto]

The previously scheduled[1] 3.6.23 -> 7.0.1 advertised update[1] is now postponed while we make sure our server capacity is sufficient for release. Once the investigation is complete I will communicate a new date well in advance so all stakeholders can plan accordingly.

I apologize for any churn this may have caused.

Thanks,
Christian

[1] https://wiki.mozilla.org/Releases#Other_releases
[2] http://christian.legnitto.com/blog/2011/10/03/reminder-firefox-3-6-23-7-0-1-advertised-update-scheduled-for-thursday/

[PhillipJones]

Are you aware of this:
http://www.tomsguide.com/us/mozilla-Firefox-7-browserwars,news-12791.html
Sounds like 7.0 and 7.0.1 are causing major breakage especially sync
services.
Some of you better read the Mozilla general news group for a while.

I myself am on the alpha channel update Program. I can tell you at least
the Mac version of 7/7.0.1 had a lot of problems some extensions that
wouldn't work. In version 8 suddenly started working despite being shown
incompatible.


--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net mailto:pjo...@kimbanet.com

[Ron Hunter]

On 10/6/2011 7:20 PM, PhillipJones wrote:
> Christian Legnitto wrote:
>> The previously scheduled[1] 3.6.23 -> 7.0.1 advertised update[1] is
>> now postponed while we make sure our server capacity is sufficient for
>> release. Once the investigation is complete I will communicate a new
>> date well in advance so all stakeholders can plan accordingly.
>>
>> I apologize for any churn this may have caused.
>>
>> Thanks,
>> Christian
>>
>> [1] https://wiki.mozilla.org/Releases#Other_releases
>> [2]
>> http://christian.legnitto.com/blog/2011/10/03/reminder-firefox-3-6-23-7-0-1-advertised-update-scheduled-for-thursday/
>>
>
> Are you aware of this:
> http://www.tomsguide.com/us/mozilla-Firefox-7-browserwars,news-12791.html
> Sounds like 7.0 and 7.0.1 are causing major breakage especially sync
> services.
> Some of you better read the Mozilla general news group for a while.
>
> I myself am on the alpha channel update Program. I can tell you at least
> the Mac version of 7/7.0.1 had a lot of problems some extensions that
> wouldn't work. In version 8 suddenly started working despite being shown
> incompatible.
>
>

Funny, I ran FF7 beta for a long time with no sync problems, and I am
running FF8 beta with no sync problems other than an overloaded server.
You can't blame FF for Mozilla's sync server being overloaded. That's
like blaming your car because you don't have a 10 car garage.

[Daniel Veditz]

On 10/6/11 5:20 PM, PhillipJones wrote:
> Christian Legnitto wrote:
>> The previously scheduled[1] 3.6.23 -> 7.0.1 advertised update[1]
>> is now postponed while we make sure our server capacity is
>> sufficient for release.
>

> Are you aware of this:
> http://www.tomsguide.com/us/mozilla-Firefox-7-browserwars,news-12791.html
>
> Sounds like 7.0 and 7.0.1 are causing major breakage especially sync
> services.

That is indeed the server whose capacity needs to be deemed
sufficient. There's absolutely no problem with the release/update
servers.

[Philipp von Weitershausen]

On Thu, Oct 6, 2011 at 6:00 PM, Ron Hunter <rphu...@charter.net> wrote:
> Funny, I ran FF7 beta for a long time with no sync problems, and I am
> running FF8 beta with no sync problems other than an overloaded server.  You
> can't blame FF for Mozilla's sync server being overloaded.  That's like
> blaming your car because you don't have a 10 car garage.

That made me LOL. Although a more accurate car analogy would involve
traffic. Firefox 7 goes out to the shops to buy fresh milk way more
often than Firefox 6. This is great because you always have fresh milk
at home and it's fine when only a few people do it (like when 7 was in
beta). But it causes more congestion than anticipated when everybody
does it.

That's not even the biggest problem, though. Increased load was
obviously anticipated. The straw that broke the camel's back was that
-- if I may stick with the traffic analogy -- Firefox 7 should be
listening to the traffic news and stay home if the roads are clogged
up. Sync was designed to do that, but the functionality was broken,
untested, and (fortunately!) never needed until this week. We have
landed fixes for that in all channels but release now.

Also, Firefox 9 and later also has a much better UI treatment of these
issues (not pupping up the error bars all the time). I'm personally
running Nightly and haven't seen a single bar all week. Some people
have despite running Nightly, which has helped us identify a few more
issues that we're fixing as I'm writing this. The only problem is that
those fixes will take time to bubble up through the channels so they
won't help us this week. So alas, we have to rely on our fantastic Ops
team to ramp up many more servers -- sorry, build more highways -- and
make the existing ones run smoother. They've been doing that around
the clock and it seems we're starting to see the light at the end of
the tunnel.

[Robert O'Callahan]

On Fri, Oct 7, 2011 at 3:40 PM, Philipp von Weitershausen <
phil...@googlemail.com> wrote:

> They've been doing that around
> the clock and it seems we're starting to see the light at the end of
> the tunnel.
>

Yeah, I was getting 4-6 Sync errors per hour, but the last one was an hour
ago. Thanks!

Rob
--
"If we claim to be without sin, we deceive ourselves and the truth is not in
us. If we confess our sins, he is faithful and just and will forgive us our
sins and purify us from all unrighteousness. If we claim we have not sinned,
we make him out to be a liar and his word is not in us." [1 John 1:8-10]

[Axel Hecht]

Reminds me, we did this before:

The live-bookmarks code goes in and updates about every hour. Though, in
case of network problems, it used to try more eagerly, and never backed
off. It does today.

Reason: One of our localizations overloaded a news server, as we're
shipping a default newsfeed for the bookmarks toolbar. So, they made
that overloaded feed url a 404. Firefox started to pull more often in
return, bad fox. Didn't help that their 404 page was larger than their
RSS feed, too.

Lesson not learned apparently: If you occasionally hit a server, and it
runs into trouble, try again. Once. Then give the server a break.

Axel

[PhillipJones]

I ma not blaming anything I am just reporting. BTW at least One bug
report of FF that its broken has been reported. (and not by me)

My regular version is 3.6.23 I do test the alphas.
I used the 7.0.1 for a while noted many of my extensions didn't work
even addon compatibility reporter even after its latest update. However,
when I updated to the 8.x alpha many of the no working extensions began
to work even compatibility reporter. The one I missed the most in FF
was NoSquint and it was broke in 7 but not 8 and no change version. I
also Try out the Alpha channel for SeaMonkey. The latest version of SM
2.5.1 No Squint is broken.

[Ron Hunter]

When I read how FF7 would handle sync, I ASSUMED that the folks who ran
the sync servers would be prepared for the additional traffic before
release. True to form, assuming didn't get it. Really hasn't greatly
impacted my operation, since syncing requires that I be changing
something, which I haven't, and rarely do. Of course, the program
doesn't KNOW I haven't changed something unless it checks the server.
Maybe, for those of us with local nets, a local server could lighten the
load. That is, allow passing this information locally to networked
machines. I guess that would still require some access to the outside
server at some point.
I am sure next time something like this is implemented, someone will
give a heads up to the server folks, right? Grin.

[beltzner]

Oops, accursed reply vs. reply all!
On Oct 7, 2011 8:27 AM, "beltzner" <mbel...@gmail.com> wrote:
> Hi,
>
> Moderator of this group, here. Please keep this thread on topic, which is
to
> say about the planned schedule for the update. If you have Add-on
> compatibility bugs, please either file them, bring them up with the Add-on
> author, or start a thread in dev-platform about what caused the bustage.
>
> thanks,
> mike