For better communication when the team is fixing/working on when during maintenance? Whether its extended or additional?
I think frequent summarised updates would be appreciated
For better communication when the team is fixing/working on when during maintenance? Whether its extended or additional?
I think frequent summarised updates would be appreciated
Look at the top of the forum page. It’s the very first post.
Otherwise look under News and you will see patch notes.
Doesn’t get much more informative than that.
Apparently not
Take for example yesterday there was a problem with the high explorer title and they made some class adjustments, they could put it on the log in screen where to find the info if they are unable to sum it up in a short paragraph.
Why? It’ll be boring technical crap.
Yeah. Most people won’t understand the intricate details on what they or doing or how. I know I certainly couldn’t. People just need to hear “we are working on x so that you can do y” and that’s it.
It’s fine how they do the post as they r done for years.
From the POV of an IT professional that does maintenance at times you can summarize what the main point of maintenance is for but there could be a dozen little details that have to be done along the way. Yeah we don’t say that in the summary that’s for the post maintenance report.
Most hotfixes I imagine would be pretty uninteresting.
Nobody really cares about cleaning up code to make a tiny piece of the game 3% more efficient.
Absolutely this too.
I don’t know if the details would necessarily be useful to us. There is a tendency to panic or think the worst when we do get communication.
I can go both ways here.
On the one hand, I’m a software engineer by trade. Seeing how another team negotiates something like this could be enlightening and useful.
But on the other hand, I get a bellyful of that krep in my daily 9-5. Do I really want to see more during my time off?
I’m a tester. I feel like it would be like reading my teams chat during a rough implementation.
As a service IT professional, you don’t care and wouldn’t bother reading it past the first week of documented changes.
Wanna know why? Because it’s boring, you might not understand, or both.
Just do a crossword or something while you wait for prod to come back up.
I can’t think of any worse way to use your time than comb through tickets/documentation if it’s not necessary.