I like these options. Master could be renamed “current” to put it higher up, though with the rest of the naming scheme here, it would be nice to sort before the issue branches. This is more of a universal sorting issue than just the GitHub UI (think git itself, or gitbox, or any external tooling).
— Matt Sicker > On Oct 9, 2022, at 07:02, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hello, > > Since now the structure of `master` and `release-2.x` are similar, > I'll be checking `log4j-api`, `log4j-core` and `log4j-1.2-api` to see > if we forgot to apply some bug fixes to `master` (I certainly did). > > It might also be the right moment to switch back to `master` as the > default branch and perform some naming changes to ensure that Github > lists the branches in order of importance. > > Github seems to sort branch names lexicographically in the C locale > (digits, uppercase letters, lowercase letters) with some exceptions > for numerical values. > > E.g. we can: > > * rename `master` to `main` (the default Github name on new repos), > for those sensitive to the name `master`. > * rename `release-2.x` to `2.x`, `log4j-2.3.x` to `2.3.x` and > `log4j-2.12` to `2.12.x`: GitHub's ordering will be `2.x -> 2.3.x -> > 2.12.x`. > * rename the feature branches to > `LOG4J2-issue_number/optional_mnemonic`. I really would like the > `/optional_mnemonic`, because I don't remember issue numbers. > * we can ask the authors to close some feature branches or move them > to their fork, if they are obsolete. > > Piotr
