Wow, that was a quick response to my request )))))

I think some better status updates would really be beneficial.

It says GRID STATUS: ONLINE
Online Now: 8017 (and falling)

* Grid status should be yellow, saying like DIFFICULTIES or UNSTABLE (also ROLLING RESTART and such).

* There should be a link to the status page, somewhere in the upper right corner of the sl web or in the main menu line. Or just below the L$ and get land. Hell, above. I know for a passer-by it doesn’t look good if the status is not green, but users would appreciate it.

* In-world notices for new blog entries would be nice, plus when service related entries are updated. I am considering making a group for this, but I suppose LL should provide this so it would be reliable and timely.

As can be seen from the responses here, people will be much less aggravated if there will be more interaction

I look forward to the post which explains what actions you’ve taken to prevent a recurrence.

Anyone want to go inworld and apologise to my students at Strayling for “abandoning” them??

*sheesh*

Thumbs up for some decent communications from the lab for once.
We love to get the full story guys, please continue that way in the future and we will all have a better understanding for the problems instead of just getting furiously mad about your lack of communications. *wink*

How about doing the upgrades in two steps. First upgrade some quieter sims and some sims that user would opt in (get a discount maybe). OK, with 4 sims per server this could be tricky to manage and I see you want to roll out as quickly as possible. But is that a good strategy?

Sure, it wouldn’t trigger all the problems (like the one with slow connection cleanup), but while you have a good beta cycle with RC previews, the same is not well managed for servers.

“That’s a great sentiment. At least for now it’s not practical as we do want to keep the platform moving forward. ”

Josh - about taken a day between releases - it isn’t a sentiment - it’s sound practical advice and really a requirement….

We all know that sometimes we need to take a step back to move things forward. We also all know that after a stressy time - we need to kick back a little before we proceed. We have to feel that we have accomplished something - and more importantly - BE ALLOWED to feel we have accomplished something. Thats from the human side of things…

From the tech side of things…

If you don’t stop for a while and get your house in order - things get confused and bad things happen. you’ve seen this before in the past. The tech side needs to settle - it needs to acheive it’s regular operational state.

Take that day to plan and interpret what you have seen. Use it to start to get control and understand what changes on one side affect in the other.

Good luck with the next release and we hope that you continue to post the post-mortems - REGARDLESS of if they turn into a debacle or storming success…

Openess is the way forward - perhaps more so than anything else?

Chris

Thank you very much for the full explanation. Being one of those readers with a technical background myself, I can fully appreciate the insane three day triage of the situation that your technical teams went through. I’ve gone through a few of those myself, and they are NOT fun.

Let’s hope that everything learned during the updates will make SL a better place to live in in the future.