(08-18-2017, 08:54 AM)37thchamber Wrote:Considering this appears to be a clerical error, who are the FO supposed to be coming down hard on?
I mean, obviously something needs to be done, but it sounds like you want to see some kind of punishment... which would appear to be counterproductive at this stage, given that the only people it could affect have done nothing wrong.
The problem is something like this slipped by multiple people for 11 weeks. It wasn't until a TE production article called it out, which was the cause of this article. It just seems weird that multiple people never noticed this, and seems like they could at least make sure updaters know how to do their jobs. It's hard to see such a sizable mistake just slipping by everyone involved with the team.
[div align=center]
![[Image: HzftG7t.gif]](https://i.imgur.com/HzftG7t.gif)
![[Image: YltEe9n.png]](https://i.imgur.com/YltEe9n.png)
[div align=center]
![[Image: HzftG7t.gif]](https://i.imgur.com/HzftG7t.gif)
![[Image: YltEe9n.png]](https://i.imgur.com/YltEe9n.png)
[div align=center]