You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the gemctp7user tools repo we rely on being able to specify a release version and getting the corresponding files.
Currently, this is muddled by mixing different era files within a given "release".
While understandable from a pre-release perspective, it would be best if when a release becomes "final" it always has the same convention.
The expectation (based on previous releases) is that this will always work:
If some of this is obsolete (i.e.,, using the _GBT suffix), that's fine, but the general structure needs to be consistent (see also cms-gem-daq-project/xhal#27)
The text was updated successfully, but these errors were encountered:
In the
gemctp7user
tools repo we rely on being able to specify a release version and getting the corresponding files.Currently, this is muddled by mixing different era files within a given "release".
While understandable from a pre-release perspective, it would be best if when a release becomes "final" it always has the same convention.
The expectation (based on previous releases) is that this will always work:
If some of this is obsolete (i.e.,, using the
_GBT
suffix), that's fine, but the general structure needs to be consistent (see also cms-gem-daq-project/xhal#27)The text was updated successfully, but these errors were encountered: