We're using revision 4681 of the web client, which corresponds to the 6.0.3 release (tagged as such).
This is on a production server, so we do *not* want to incorporate all of the latest commits to the 6.0 series branch (stable) as that would mean introducing potential new bugs/side-effects. So, we want to stick to the release revision, with patches for specific bug-fixes applied as necessary. That's the reason well tested revisions are tagged as release versions.
Could you please check revision 4681 (tag:6.0.3) of the web-client for this bug, and provide us with the patch that fixes this specific bug.
Hi Amit,
We're using revision 4681 of the web client, which corresponds to the 6.0.3 release (tagged as such).
This is on a production server, so we do *not* want to incorporate all of the latest commits to the 6.0 series branch (stable) as that would mean introducing potential new bugs/side-effects. So, we want to stick to the release revision, with patches for specific bug-fixes applied as necessary. That's the reason well tested revisions are tagged as release versions.
Could you please check revision 4681 (tag:6.0.3) of the web-client for this bug, and provide us with the patch that fixes this specific bug.
Thanks and regards,
Deepak