Update RELEASE.md

[vishi24]

No description provided.

[vishi24]

@faizmagic ,please review and merge.

[faizmagic]

I have reviewed the release notes, and recommend the following changes

1. we need to add more details about the features which ONIX ver 0.2 is offering, currently, just mentioning a one liner following description will not help
   a . This release is specifically tailored to make the deployment of individual components possible.
2. In the limitations section i see that, its still mentioned that "The current version installs all the components on the docker", is this not for ver 0.1
3. Add the following limitation " support only vertical scaling horizontal scaling (ECS / EKS) is planned for upcoming release"
4. when installing individual components, registration with the registry has to be done manually, this is explicitly done to avoid confusion and to prevent the network with incorrect or wrong registrations.
5. why is in the upcoming release section, following has not been updated.
   • Installation of individual components with user-provided configuration.
   • Support for Windows and Mac OS will be added.
6. By the way how are we managing the version release, are we adding all release details in a single release.md file, if so what will happen to the old release notes (ver 0.1).
7. where is the link to ver 0.2 milestone, which points to the list of issue tickets

[vishi24]

@faizmagic Requested changes done.

[faizmagic]

As discussed lets have the following changes in place

1. we should have provision to archive all release notes in a separate folder and link to the current release notes through the previous releases section.
2. create a folder called releases folder and archive all old release notes with proper naming like release_ver0.1.md
3. The current release notes will stay in the existing release.ms file