Subtree repository workflow

Major version (eg: 3.0)

1. Create a new release milestone
2. Create a new <version> branch from the <previous-version> branch
3. Update <previous-version> references to <version> in documentation
4. Create a new ISSUE-<issue> branch from the <version> branch
5. Implement/fix issue
6. Create pull request from the ISSUE-<issue> branch to the <version> branch
7. Merge pull request
8. Repeat step 3-6 for more issues
9. Subtree split the component directory to branch <subtree-repository-name>-<subtree-version>
10. Push the branch <subtree-repository-name>-<subtree-version> to the subtree repository branch <subtree-version>
11. Create release for main and all component repositories

Minor version (eg: 3.1)

1. Create a new release milestone
2. Create a new <version> branch from the <previous-version> branch
3. Update <previous-version> references to <version> in documentation
4. Create a new ISSUE-<issue> branch from the <version> branch
5. Implement/fix issue
6. Create pull request from the ISSUE-<issue> branch to the <version> branch
7. Merge pull request
8. Repeat step 3-6 for more issues
9. Subtree split the component directory to branch <subtree-repository-name>-<subtree-version>
10. Push the branch <subtree-repository-name>-<subtree-version> to the subtree repository branch <subtree-version>
11. Create release for main and all component repositories

Patch version

1. Create a new release milestone
2. Create a new ISSUE-<issue> branch from the <version> branch
3. Implement/fix issue
4. Create pull request from the ISSUE-<issue> branch to the <version> branch
5. Merge pull request
6. Repeat step 2-5 for more issues
7. Subtree split the component directory to branch <subtree-repository-name>-<subtree-version>
8. Push the branch <subtree-repository-name>-<subtree-version> to the subtree repository branch <subtree-version>
9. Create release for main and all component repositories