Remove or keep symbolic links to latest stack envs?

[rickgrubin-noaa]

Is your feature request related to a problem?

The spack-stack wiki / Preconfigured Sites / Overview states:

Note. To support users who consistently want the latest release, on NOAA RDHPCS tier 1 platforms, soft links pointing to the modulefiles associated with the latest release of the Unified Environment are provided under the main spack-stack directory. The usage consists of module use /path/to/spack-stack/latest-ue-, and then loading the spack-stack meta-modules as usual. These soft links should be updated when each release is finalized.

After installing spack-stack-2.0.0 on various EPIC hosts, an examination of these symbolic links showed them to be quite outdated. Most links pointed to spack-stack-1.8.0, and none pointed to the most recent previous release of spack-stack-1.9.3.

It would seem that the use of these links has fallen into disuse. Given that the symlinks were outdated, and nobody 'complained,' are they still needed?

Describe the solution you'd like

Determine whether or not the continued creation of these symbolic links is pertinent / relevant.

Additional context

While maintaining these symlinks is not difficult, it is one more task that requires remembering to do -- as tasks for releases go, it's not part of the release template.

[AlexanderRichert-NOAA]

@aerorahul @DavidHuber-NOAA did you ever try using these? Are/were they helpful?

[DavidHuber-NOAA]

@AlexanderRichert-NOAA no, we never did. We have always pointed to the explicit version we want to work with.