Someone messing with the fonts?
Discussion
Dan_1981 said:
........... and also the other guy Eybic who got the job to look after forums & users seems to have disappeared too.
Edited by Dan_1981 on Wednesday 5th August 08:27
Edited by Dan_1981 on Wednesday 5th August 08:30
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.
Du1point8 said:
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.
Absolutely spot on, I had assumed this was standard practice these days
BenWRXSEi said:
Sorry, but I couldn't resist screen-shotting how that post showed for me 
hornetrider said:
Indeed.
One kind of assumes this is what is being done as it's testing 101, but then you get stuff like this happening and you think, they're not... I mean, they haven't... have they really just...?
One kind of assumes this is what is being done as it's testing 101, but then you get stuff like this happening and you think, they're not... I mean, they haven't... have they really just...?
king ad...Cotty said:
Ahh so its not just me getting light blue and purple coloured fonts
I'm now getting these new 'neon' colours on the desktop version when viewing threads, but no where else...Colours are completely wrong too, I realise this isn't a Gok Wan fan club forum but it wouldn't help to hire a graphic designer for a couple of hours...
anonymous said:
[redacted]
I agree, and there are assumptions in your post that are not correct.The issue was with the release and regression process that was not followed correctly, which caused the code to go live without going through the DR version properly. The changes to CSS when viewing were caused by the release itself, and not developers changing code on the live site - two systems were getting confused with device and skin detection and thus creating numerous combinations.
I have started a new thread for any of the current issues and will close this one to keep everything in one place
http://www.pistonheads.com/gassing/topic.asp?h=0&a...
Gassing Station | Website Feedback | Top of Page | What's New | My Stuff