I am a developer interested in contributing to a Rocky Linux Special Interest Group (SIG) that builds packages. I need to understand the version control best practices. Please navigate to the 'Branch Names' section under 'Managing Content' in the SIG Guide. Explain the purpose of the 'main' branch, the naming convention for 'release' branches, and how 'topic' branches should be used. Additionally, identify the expected format for 'Tagging' within the Rocky Linux GitLab.
Navigate to 'https://wiki.rockylinux.org/sigs/sig-guide/managing-content/importing-to-the-rocky-linux-gitlab/'. Click on the 'Branch Names' link (ID 225). Identify the purpose of the 'main' branch as described on the page. Note the naming convention and purpose for 'release' branches. Describe how 'topic' branches are expected to be used. Click on the 'Tagging' link (ID 233). Identify and describe the expected format for 'Tagging' on the Rocky Linux GitLab. Synthesize all collected information regarding branch names and tagging into a concise answer.
The agent successfully navigates to the 'Branch Names' page. The purpose of the 'main' branch is stated as 'the latest development of the package and should be used for new feature development or bug fixes that are not tied to a specific release'. The naming convention for 'release' branches is stated as 'rX' (e.g., 'r8', 'r9') and their purpose is 'for stable releases of the package for a specific Rocky Linux version'. The usage of 'topic' branches is described as 'for short-lived feature development or bug fixes that will be merged into 'main' or a 'release' branch'. The agent successfully navigates to the 'Tagging' page. The expected format for 'Tagging' is stated as 'vX.Y.Z' (e.g., 'v1.0.0') for releases and 'vX.Y.Z-rcN' (e.g., 'v1.0.0-rc1') for release candidates.