BBM for Android and iPhone will not be released this week

by Volker Weber

We attempted to address the problems caused by the unreleased version throughout the day on Saturday, but as active users of the unreleased app neared a million - and accelerated - it became clear that the only way to address the issue was to pause the rollout for both Android and iPhone.

Let me get this straight. There was an old version causing problems. As people were waiting for BlackBerry to release the new version, more people used the old version. So you let them wait a little more. And yet more people started sharing the old version instead of being able to use the new version you did not release.

Nobody would have been able to see that coming, right?

More >

Comments

Release management is a miracle.

Bodo Menke, 2013-09-23

"Let me get this straight." Straight as a streak of lightning. There are other reasons which you've missed.

Can you say "Test/Debug" code?

Dragon Cotterill, 2013-09-24

My assumption is that you test and debug code before announcing its availability. If you are still testing and debugging after announcing a launch, that would be an additional problem.

Volker Weber, 2013-09-24

You assume correctly. But that "old" version was not something we officially released. When you have an official one that is getting swamped by test/debug data from something that should never have been in the wild, then there is a problem.

Personally I'd like to string up whoever released it. It only harms the Users and BlackBerry.

Dragon Cotterill, 2013-09-24

Yes, absolutely. And also the Crackberrys who promote it. My thinking is that these people would drop their pre-release as soon as they get something with a higher version number.

Volker Weber, 2013-09-24

I would imagine that proper development would allow them to detect which version client is trying to login and disable the "non-official" version.

But then, "proper development" is the key phrase here.

Craig Wiseman, 2013-09-24

Recent comments

Volker Weber on AP Steering in der nächsten Fritz-Software at 20:08
Moritz Petersen on AP Steering in der nächsten Fritz-Software at 20:02
Patric Stiffel on Soyuz-Flug zur ISS und zurück at 18:35
Volker Gronau on AP Steering in der nächsten Fritz-Software at 17:45
Axel Koerv on AP Steering in der nächsten Fritz-Software at 16:33
Volker Weber on Kleines Update zu ginlo at 12:45
Marco Siedler on Kleines Update zu ginlo at 12:43
Stephan Perthes on Soyuz-Flug zur ISS und zurück at 11:45
Bill Buchan on Ein kleines persönliches Update at 10:05
Oliver Regelmann on Is Watson Workspace dead or only resting? at 09:02
Oliver Barner on Unfallfolgen :: Ab jetzt geht es bergauf at 09:01
Henning Kunz on Ein kleines persönliches Update at 08:59
Christian Tillmanns on Soyuz-Flug zur ISS und zurück at 08:41
Richard Schwartz on Huntress at 04:10
John Keys on ginlo auf Android at 22:54
Amy Blumenfield on Unfallfolgen :: Ab jetzt geht es bergauf at 20:55
Stephan Perthes on Last-Minute-Geschenk :: udoq-Qi-Lader at 19:51
Johannes Koch on Words to live by at 19:29
Volker Weber on ginlo auf Android at 18:45
Wolfgang Kulhanek on ginlo auf Android at 18:40
Sami Bahri on ginlo auf Android at 17:45
Volker Weber on Words to live by at 17:23
Jens Nullmeyer on Words to live by at 17:17
Volker Weber on Soyuz-Flug zur ISS und zurück at 17:14
Maik Endler on Soyuz-Flug zur ISS und zurück at 15:31

Ceci n'est pas un blog

I explain difficult concepts in simple ways. For free, and for money. Clue procurement and bullshit detection.

vowe

Contact
Publications
Stuff that works
Amazon Wish List
Frequently Asked Questions

rss feed  twitter  amazon

Local time is 21:53

visitors.gif

buy me coffee