My reasoning behind my +1 vote is that it is good to have the log4j1
repository on git, aligned with other repositories and easily available to
the public.

As a starter, the repository should clearly mention its EOL and NOT provide
any interactivity through issues and pull requests.

--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.

On Fri, Dec 24, 2021, 09:33 Volkan Yazıcı <vol...@yazi.ci> wrote:

> +1
>
> Goal needs to be stated in bold in a README.
> Existing PRs (there are 14 as of date) need to be processed.
>
> This 1.x discussion took way more time then it should, IMHO. Let's take the
> simplest approach and be done with it. We all agreed to not accept anything
> except security fixes. Though we all know there will be incoming PRs, which
> we can all do is to reject after pointing to our goal statement.
>
> I am not keen to keep two repos of the same project around. Making a 1.x
> release is already confusing enough, having multiple repos will make things
> worse.
>
> On Thu, Dec 23, 2021 at 10:35 PM Ralph Goers <ralph.go...@dslextreme.com>
> wrote:
>
> > In https://issues.apache.org/jira/browse/INFRA-22654 Chris Lambertus has
> > recommended that we can divorce
> > the read-only SVN repo from https://github.com/apache/log4j. However, it
> > will not be able to keep the same
> > name as all Git repos owned by the logging project must start with
> > “logging-“.
> >
> > So this vote is to:
> > 1. Delete the apache/logging-log4j1 repo I created last night.
> > 2. Divorce the apache/log4j repo from SVN.
> > 3. Rename apache/log4j to apache/logging-log4j1.
> > 4. Create a branch named “main” from the v1_2_17 tag.
> > 5. Make main the default branch in GitHub.
> >
> > While all votes are welcome Infra needs consensus from the PMC on this
> > vote so the result will separate
> > binding from non-binding votes.
> >
> > Ralph
> >
> > PS - I’ve separated this from the previous vote thread since it was
> mostly
> > discussion. If you want to discuss
> > this please prefix the subject with [DISCUSS]
>

Reply via email to