Someone messing with the fonts?
Discussion
Ollie_M said:
Just to let you know we have launched a new 'skin' for the website that's why you might be experiencing a few changes in fonts and layout.
Please feel free to share your opinions as your feedback is vital to the continued development of the site.
Why is PH the only website Im aware of that releases code/changes on the live site?Please feel free to share your opinions as your feedback is vital to the continued development of the site.
Whats wrong with having a UAT site and testing on there, why always the Production site and wait until someone goes insane from staring at the awful 'new skin'?
Craikeybaby said:
Craikeybaby said:
I switched off beta 2 skin as I found it less intuitive than the mobile beta skin, but I guess there's no going back now.
My main problems are that in the "my stuff" view on my iPhone there is no longer an indication of which threads have been updated since your last visit (updated threads were previously in bold) and there's no button to take you to the first unread post. Both were features I used regularly.
The first point seems to be fixed now!My main problems are that in the "my stuff" view on my iPhone there is no longer an indication of which threads have been updated since your last visit (updated threads were previously in bold) and there's no button to take you to the first unread post. Both were features I used regularly.
In defence of PH this was being tested for a while - available to everyone, but not sure where it was communicated or where feedback should have been sent to. I tested it briefly, but stopped using it as it wasn't very intuitive.
Thats like when the off shore team tell me its tested and I find out the data is hardcoded and it has never worked.
This shouldn't be a development issue, this is a change management release of locked down, 'tested' code that has not changed for a good few weeks whilst in UAT/OAT stages.
In those stages the release should have been tested on a like for like DR version of Prod to make sure the release is working fine.
If that is not done then a roll back script should be activated to put it back to the previous working prod copy.
What you don't do, is keep the system live and do ad-hoc fixing in a Prod environment, if that is what the Development/Release team are doing, then someone needs to have a word as that is a disgraceful practice and if anyone in my team did that to any of my prod environments, they would be out of the door ASAP.
In those stages the release should have been tested on a like for like DR version of Prod to make sure the release is working fine.
If that is not done then a roll back script should be activated to put it back to the previous working prod copy.
What you don't do, is keep the system live and do ad-hoc fixing in a Prod environment, if that is what the Development/Release team are doing, then someone needs to have a word as that is a disgraceful practice and if anyone in my team did that to any of my prod environments, they would be out of the door ASAP.
Gassing Station | Website Feedback | Top of Page | What's New | My Stuff