RSVC Automated Features

Step-by-step GitHub release plan for the RSVC Automated Features:

Release Plan for RSVC Manual Release

1. Merge Changes to Main:

Open GitHub Desktop and ensure you are on the correct branch (e.g., 13.1.37). Go to the main branch and create a new pull request. Compare changes across branches (main to 13.1.37). Create the pull request, ensuring it can be merged automatically. Merge the changes to main.

2. Tagging the Release: In the main branch, create a new tag for the release (e.g., 13.1.37-ABC). Include a meaningful description like "Release version 13.1.37 with features A, B, and C."

3. Push Changes to GitHub: Push the changes to GitHub, including the new tag.

4. Verify the Release: Go to the GitHub repository and ensure the new tag is visible under releases. Verify that the release information accurately describes the changes made.

5. Repeat Steps for Subsequent Releases: Repeat the above steps for subsequent releases (e.g., 13.7.15-A).

6. Consideration for Future Releases:

Discuss and decide on a consistent versioning and tagging strategy. Document release procedures and FAQs for the team’s reference. Explore the use of explicit tags to differentiate between A, B, and C releases.

Notes: Be cautious with branch naming to avoid conflicts with tags. If there are major changes involving file renames, consider waiting until the entire version is complete before merging into main. For explicit tags (e.g., A, B, C), use a consistent and clear naming convention. Consider creating a detailed FAQ or documentation to address common questions and procedures related to releases.