version document

New Versions directory with following structure:

• LHCb
  • 2024.Q1.2.v0.0.json
  • run5-v00.00.json ...
• VP
  • 2024.Q1.2.v0.0.json or
  • list.json ...

In the LHCb directory, combining the versions of all component used, there will be a file per version. They

In the components there are two options, to have a file for each version or a single file for all versions, in which case they will be in decreasing order with the more recent version on top

Script: combine the information from each component for given LHCb version, need previous version given by hand. Possibly also specify for which Run it is, i.e Run3, Run4 or Run5

---

Fields in versions file for each component and version:

• version
• data-taking periods, e.g. run3, this is a list as some components can be the same, e.g. magnet
• description, i.e. short 1-2 line explanation of what in the version
• comments, i.e. longer more detailed information, e.g. what is the difference with respect to previous version

---

Fields in versions files for LHCb:

• overall data-taking period, run3/run4/run5, to be entered/edited by hand
• description, i.e. short summary of what the combined description is, to be edited by hand
• list of components used, for each
  • comp_name,
  • comp_version,
  • comp_description
  • flag when new/different from what used in earlier version
• section on previous version difference with list of components that changed version
  • prev_comp_name,
  • prev_comp_version,
  • prev_comp_description

---