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 an
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
Hi Matt,
On Sun, 9 Oct 2022 at 18:27, Matt Sicker wrote:
>
> (...) This is more of a universal sorting issue than just the GitHub UI
> (think git itself, or gitbox, or any external tooling).
You are right, I tried the git executable, Eclipse and GitHub and they
all seem to use lexicographic ord
+0. I really don’t care. However, I would only be in favor of switch
master/main/whatever to be the default if we are going to create a release.
Personally, I’d prefer to be discussing how we are going to change the web site
to support both 2.x and 3.x releases and make a plan to get the web sit
I asked some people in infra how we should handle our site since it’s currently
a huge git repo. There was a suggestion of using the nightlies site publishing
area with a CNAME which might work. Otherwise, we need to look at what other
PMCs are doing with multi-version websites.
—
Matt Sicker
