[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464530#comment-17464530
]
Volkan Yazici commented on LOG4J2-3272:
---------------------------------------
I think the PMC is onboard with the idea of accepting 1.x contributions with
the condition that they should only address CVEs and nothing else. I also see
(and agree with) your point regarding the downside of having two 1.x repos. We
further stated that we are extremely occupied with other priorities related to
2.x, which we feel more responsible for compared to a version that has reached
its EoL in 2015. For the records, we have a life and day job too. Given all
these, I find the tone of your remarks, style of communication, accusative and
attacking.
Since Ralph is still not online, we don't know why he created a new repo rather
than reusing the old one. I'd wait to hear his rationale before taking any
steps.
I can't speak for others, but I see the merit of your goal and I agree with it.
I will do my best to help you with them. We just need time to wrap up things on
the 2.x front.
> Enable Git and GitHub for log4j 1.2 repository
> ----------------------------------------------
>
> Key: LOG4J2-3272
> URL: https://issues.apache.org/jira/browse/LOG4J2-3272
> Project: Log4j 2
> Issue Type: Task
> Reporter: Vladimir Sitnikov
> Assignee: Ralph Goers
> Priority: Blocker
>
> Please enable Git and GitHub for log4j 1.2 repository so it is easier to
> suggest and test changes.
> Every patch to 1.x must be well-tested, so attaching SVN patch files to JIRA
> is a recipe for disaster
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
