Revisions in SCl-HCL and Binaries
Have often seen this change in SCL-HCL and was wondering how this SCL-HCL can get updated with mino/major changes post Final release of product !
Does Binaries also gets updated on fileconnect respective to the updated SCL-HCL?
Has anyone noticed this behaviour.
Hi Vaibhav,
Sorry for the late response. I think we may have a language barrier but I will attempt to give you the information I think you're looking for.
Once we post binaries to file connect, they NEVER change. If we need to update, they will always get a new filename/version number.
If we update the SCL to say that something is supported, and we did NOT say that that "something" was supported in the previous revision of the SCL, we are only adding to what we support. We will not have changed ANY binaries on File Connect. So if you have already downloaded, there is no need to re-download them again because they will be exactly the same as before. We did not release a hotfix which includes the support; we are saying that it probably ALWAYS worked, but here is our formal declaration and blessing that it is a supported configuration. Does this clear it up?But it is also unfair for front end representatives to commit respective to customers app against symantec solution.
I mean no offense, but I cannot figure out what you're saying here. :) If you still have reservations, please rephrase and ask again - I'll do my best to give you an answer!