This measure aims to accomplish the following:

• Rename the 'master' branch on GitLab and GitHub to 'v10'.
• Set an implicit standard where we no-longer use vague names like 'master' or 'main', but instead our branches are always based on version numbers and features. E.g. 'feature_keywords_v11' would be the development of a new feature for later implementation. E.g. 'v11' would be the main version 11 branch where releases are conducted. E.g. 'bug_keywords_v11' would be a branch aimed at fixing a bug in v11.
  • Official version branches will start with the version in its name; branches aimed at development of features or fixing bugs will have the version at the end. This is so the maintenance status page on the homesite (which is automated) does not classify feature/bug branches in the list of releases.
• Set the 'v11' branch as the new default branch so whenever someone visits the Composr GitLab or GitHub, they will see the v11 branch by default.

The reasoning for these changes are the following:

• Get rid of outdated language ('master') in branch names and stick to concise names for clarity
• Since v10 is long-term maintenance, I would like development priority to be v11. As such, setting the v11 branch as the main one will grant it exposure to everyone who first visits the GitLab/GitHub repository, and therefore will see it / be more likely to contribute to it.

The results of this measure are considered null and void, and a re-vote will be cast.

See

Re-vote on previous two measures to be conducted

The two previously voted measures are considered **null and void**, and a re-vote will be launched on October 1, due to a software bug. Click to read more.

View