3

There is no recognized and commonly used standard for that. I suppose that you ask this question in order to avoid all the mistakes you may do by reinventing the wheel. In order to avoid those mistakes, you may be interested in checking the following: The logging format (and logging tools) of the operating system. The way you log in syslog is not exactly ...


2

You may be able to find such guidelines on a per-industry basis. NATO, NASA may have guidelines (although I don't have concrete examples). Large companies may have some guidelines. I write embedded code for the medical device industry. I have created my own error reporting format based on Microsoft's HResult, and used it in multiple companies under ...


1

What you are referring to is colloquially called Dependency Hell and it has been a known problem since software became a thing. The most IMO common solution to this is to use semantic versioning along with backwards compatibility. The basic idea is that all packages, including yours, define their dependencies not exactly but as "this or higher version". ...


Only top voted, non community-wiki answers of a minimum length are eligible