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
To make it easier to easier to know which Slicer preview is download it would be great to include the full version for Slicer preview versions. As seen at https://slicer-packages.kitware.com/#item/6446243892ad07b0d5303577, the metadata tied to the package is "5.3.0-2023-04-23" and not just "5.3.0". The "Built date" can be confused at times with the date of the version. Most users detail the version that they are using by the full string such as "5.3.0-2023-04-23" rather than by revision or commit hash.
Current
Proposed
In the Slicer application the full version "5.3.0-2023-04-23" is also stated as the version in addition to the more specific revision number and git hash.
The text was updated successfully, but these errors were encountered:
To make it easier to easier to know which Slicer preview is download it would be great to include the full version for Slicer preview versions. As seen at https://slicer-packages.kitware.com/#item/6446243892ad07b0d5303577, the metadata tied to the package is "5.3.0-2023-04-23" and not just "5.3.0". The "Built date" can be confused at times with the date of the version. Most users detail the version that they are using by the full string such as "5.3.0-2023-04-23" rather than by revision or commit hash.
In the Slicer application the full version "5.3.0-2023-04-23" is also stated as the version in addition to the more specific revision number and git hash.
The text was updated successfully, but these errors were encountered: