STEPS HOW TO RELEASE A VERSION:

1. Analyse the site and requirements.
2. Freeze the requirements and create the issues accordingly of current version.
3. Discuss the issues of next version and list them down.
4. Add the requirements and technical implementation to each issues.
5. Mark the issues with READY, IN-PROGRESS and DONE labels. Also assign the assignee respectively.
6. Create a branch of current version e.g. 1.0.0x
7. While resolving the issues, create a feature branch - feature/{ticked-id} - description and then push the changes and create a PR.
8. Ask other contributors to review the PR and after approval MERGE the PR.
9. After this, click on Releases button on right side.
10. Click on the draft a new release.
11. Create a new tag e.g v1.0.0x, v1.1.0, etc. Follow semantic versioning.
12. Click on the auto-generate release notes. and add contributors list in body.
13. Finally, click on the PUBLISH RELEASE button.

Regarding freezing of requirements for any given release cycle.

• For example, if the current release cycle is: 1.3.x
• So before releasing 1.3.0, we should be freezing the requirements for 1.4.x cycle.
• Anything new that comes up should be parked for 1.5.x and later.
• It would be good if we can create at least 2 upcoming release plans.