When we introduced lockfiles, I noticed that e.g. when creating/updating the lockfile for different OS or different build types, it sometimes (?) updates the timestamps of the revisions. For example, I created a lockfile on Windows first and had this in my lockfile:
which has the same revision but a different timestamp.
I found in the design document, that adding timestamps was necessary to "have ordered lists of versions and revisions" but I'm not really sure what that means.
Now my question is just to clarify, if this can lead to any problems or has any side effect we should be aware of? Our CI builds work on Windows and Linux with the timestamp changes in the lockfile, so it doesn't seem to have an apparent effect. Would everything run as expected, no matter which of the two timestamps above we'd have in the lockfile or is there a situation in which it'd accidentally break?
What is your question?
When we introduced lockfiles, I noticed that e.g. when creating/updating the lockfile for different OS or different build types, it sometimes (?) updates the timestamps of the revisions. For example, I created a lockfile on Windows first and had this in my lockfile:
After updating the lockfile to also support Linux builds, it changed to
which has the same revision but a different timestamp.
I found in the design document, that adding timestamps was necessary to "have ordered lists of versions and revisions" but I'm not really sure what that means.
Now my question is just to clarify, if this can lead to any problems or has any side effect we should be aware of? Our CI builds work on Windows and Linux with the timestamp changes in the lockfile, so it doesn't seem to have an apparent effect. Would everything run as expected, no matter which of the two timestamps above we'd have in the lockfile or is there a situation in which it'd accidentally break?
Have you read the CONTRIBUTING guide?