GitHub Releases for Version Management

[dami-moj]

Hi,

I want to thank you for developing and maintaining this repository. It has been incredibly useful.

As I continue to adapt and integrate this repository, I noticed that while there is a release folder intended for archiving previous versions of radar.js, the most recent version is not included and only radar.js is being archived, potentially missing other important files.

To enhance consistency and streamline version tracking, I would like to suggest:

• Utilizing GitHub’s release feature for a more structured and accessible way to manage and document different versions of the project.
• Including the latest versions of radar.js in the release folder
  Thank you for your consideration.

[bocytko]

Thanks for the feedback @dami-moj.

I noticed that while there is a release folder intended for archiving previous versions of radar.js

Yes, it's an old decision from prior colleagues of mine. The changes in radar.js are meant to be backwards-compatible. With each version bump, the usage information is updated in the README file, but old visualizations are expected to keep on working.

Utilizing GitHub’s release feature for a more structured and accessible way to manage and document different versions of the project.

A side-effect of the current setup is that it's very easy to fork and setup one's own radar. Plus, we have a small informal community with all the linked forks. I understand where this suggestion is coming from and why separating the turnkey example from the package itself would make sense.

Including the latest versions of radar.js in the release folder

The latest version radar-0.9.js has just been added with #167. It includes the configuration changes contributed by @SoumayaMauthoorMOJ with #156, #157 and #165. Are you suggesting to provide radar.js as latest version in the release folder? What value would this provide to you?