Let's talk about customer support. It's your first line of defense when customers are affected by bugs, so it should be a very high priority.
This particular problem is not even one covered in my previous rant. They have (when occasionally bothering to respond to customer support tickets) mentioned that there were issues with the process that does compilations notifying the website that compile was complete, for one or two platforms. Well, if I had to guess, I'd say the issue is now more widespread. I uploaded a build around 2 hours ago and it still hasn't been marked as completed for a single platform.
But that's not what I'm flying off the handle about, today. No, today is about Time Zones in relation to customer support.
For the uninitiated, there's this whole section of the planet in a time zone called US-East, where a shitload of people — yours truly included — live and work. And while they don't post profiles of all of their employees, we can extrapolate based on their posting habits and the occasional twitter bio, and estimate that Adobe has two teams working on PhoneGap Build: One in India, and one in San Francisco, California.
These two time zones are almost directly opposite one another, so you might think that between them they could cover customer support needs fairly well; in 12 hour blocks, with one team handing over everything to the other team at the end of the day, never going un-covered.
Woe, but were that true.
Instead, what seems to happen is that at some point in the Indian late afternoon or early evening they punch out, and the customer support portal goes dark for the night. While it does feel a bit rare, subjectively, let's say that when the SF team wakes up and heads into the office, they do in fact pay attention to the support portal. It often doesn't feel that way, as someone who's under deadlines and frustrated with a support black-out, but let's give them the benefit of the doubt for the sake of argument.
If the India team stops handling customer support at 5pm in their local time, and the SF team starts handling support at 8am in their local time, then there's a chunk of time un-covered there. At first glance that time block doesn't seem so bad. It's 5:00pm until 8:30pm in India, or 4:30am to 8:00am in SF. But if we look at that time frame for US-East, that's 7:30am to 11:00am — basically the first half of every day is radio silence.
Not just radio silence, but when a big problem happens, like, you know, NOTHING WORKS, then we're sitting on our hands and our deadlines for half a day waiting for someone, anyone, to come save the day. When my applications are useless I get a notification, and I drag my ass out of bed no matter what time it is, and I don't go back to bed until it's fixed.
This is geographic discrimination, and it suuuuuuuuucks.
And let's be honest here: they're not jumping on tickets at 8am in SF. More like 11am, if at all.
I know I sound like a broken record, here, but come on guys. This service is the fucking cats pajamas... when it works. To quote a colleague of mine, if you could keep it online we would "fly to California just to throw a stack of money at you."
For at least two weeks now they've responded to every one of my "hey, btw, your service is down" tweets, more than 12 hours later (often even 24+ hours later!), with something along the lines of "sorry, we're making some changes soon to address this!". I don't think your definition of "soon" and mine are the same.