Release naming and older versions

[wmcnCG]

Is there a way to access older releases? Why are they being removed?

I use a script to setup new machines with OpenRadioss and I often have to update the download link because the release is no longer available (this would be solved if the most recent release was always available at https://github.com/OpenRadioss/OpenRadioss/releases/download/latest/OpenRadioss_linux64.zip).

Besides this minor inconvenience, I think older releases should remain available for reproducibility.

[PaulAltair]

The suggestion of having a fixed URL for the 'latest' packaged version is a good one in my opinion, I will suggest to see if we can do that. Regarding retaining 'older' versions, OpenRadioss is effectively versionless, every pull request updates the code and there is no real specific identifier for a 'release', retaining old versions would mean keeping a copy of the download for every pull request. If you want to retain a 'version' for use later, or across multiple machines. You can obviously reuse the packaged version you downloaded. Or if you create your own fork, it remains at the state in which you forked it, until you specifically sync it back up with the main repository updates.