[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464783#comment-17464783
]
Matt Sicker commented on LOG4J2-3272:
-------------------------------------
Speaking of naming pedantry, if you're hoping to modularize v1, that should go
in a 1.3 release at minimum given the huge change in packaging. A 1.2.x release
should make minimal changes to fix CVEs and go dormant again until the next
CVE. Everything else here is jumping ahead. Maybe a release or two will attract
some more committers who can help form a healthy community in the project to
continue maintaining it, but right now, it just seems like running in circles.
> 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)
