A name like "version" should only be for tags. Once a version is released, it does not make sense to have a branch by that name, but it would be OK to have a name for a "maintenance line", as we did with "2.12.x", so here we would have "1.2.x" which is lame IMO because we're ONLY EVER going to have 1.2 releases, so it might as well stay in master/main/trunk.
Gary On Thu, Dec 23, 2021 at 9:17 AM Gary Gregory <garydgreg...@gmail.com> wrote: > WAIT, what? That does not make sense, it's the same bad name we ended up > in with the "2.12" branch instead of "2.12.x". > > Gary > > On Thu, Dec 23, 2021 at 8:50 AM Apache <ralph.go...@dslextreme.com> wrote: > >> I was already asked to create a branch off of 1.2.17. It will become the >> main branch so trunk can be left alone. >> >> Ralph >> >> > On Dec 23, 2021, at 6:41 AM, Gary Gregory <garydgreg...@gmail.com> >> wrote: >> > >> > If we use this repo, is everyone OK renaming "trunk" to "master" in >> order >> > to match the branch name of our other repos? >> > >> > Gary >> > >> >> On Thu, Dec 23, 2021 at 1:34 AM Ralph Goers < >> ralph.go...@dslextreme.com> >> >> wrote: >> >> >> >> I have cloned the read-only log4j repo to >> >> https://github.com/apache/logging-log4j1. >> >> >> >> I have followed the build instructions and had to modify the javadoc >> >> plugin to not fail on errors. Now it fails in the site plugin. >> >> >> >> If someone else wants to take this on I would suggest the first PR >> should >> >> just to the pom.xml file to get the build working as is. >> >> >> >> Ralph >> >> >> >> >> >> >> >> >>
