- Issue created by @Anybody
- πΊπΈUnited States rszrama
We're switching to a new pattern for release naming; we'll settle this up ASAP.
- πΊπΈUnited States TomTech
To be clear, we should NOT have created the 2.0.x branch initially.
We should have just created the 2.x branch. Unfortunately, it isn't possible to delete branches once they have been created.
2.x is the default branch, and all new issues should target this branch.
There is no way to "force" 2.x on the project page. Once we tag a 2.1.0 release, though, that should resolve that issue.
(And for completeness, we might have needed to create a 2.0.x branch in the future, in a specific scenario...but don't expect that to be the norm.)