[p4] Version identification in XML files

[Sheizaf, Yariv]

Hi,

A good practice is to insert the version identification (build number,
changelist number, label, etc.) in binary product files, like DLL files
and JAR/WAR files.
The "burning" of this piece of metadata is done during build of the
product file.

Now, in typical installation packages there are XML files besides the
binary (dll, exe, jar, etc.) files. 
The XML files are "sources" - their content in Perforce are identical to
the files copied into the installation set.

My question is: Is it a good idea to insert version identification
"stamp" into XML files that are delivered to customers as part of the
installer?

Benefit: Better identification of file origin in case of problem in
customer site, so the support team has an exect information.
Disadvantage: Because the files in customer site and in Perforce are not
fully identical (one or two lines are the "version identification
stamp"),
	         The QA team has another uncertainty factor during the
testing session.

Please your opinion. If you have a well-known or standard procedure
please describe it.



Regards,

Yariv Sheizaf
SAP - B1X Technical Services TL
Phone  +972-9-7779643
Mobile  +972-54-2277586