Hi there, I need suggestion and best practice for this case.
I have release an app (production/go-live), and developing for the next release.
Then a bug happened in the production server and I have to fix it.
But on developer server, our modules have undergone big changes, still in testing and maybe unstable.
Bugfixing directly on production server is a NO NO...
Any suggestion?
Thanks.
Our test/QA server also used to test the next release.
Should I deployed the old stable release version on QA server then do/test bugfixing there?
Hi Harlin.
In your current scenario you need deployed the old stable release version on QA server then do/test bug fixing but need to fix same thin your development to avoid the same issue in next release.
Regards
-SK-
I was thinking, maybe it's great if we can "fork" a released module and develop next release from that forked module.