[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464316#comment-17464316
]
Vladimir Sitnikov commented on LOG4J2-3272:
-------------------------------------------
I see [~rpopma] says
{quote} Migration to git will happen. Maybe not as fast as you would like, but
please cut the PMC some slack in this stressful time.{quote}
However, what bothers me is:
1) Many members of the PMC did respond, so they do have some time even for 1.x
2) Migration to Git is a trivial operation. It requires virtually zero effort
from the PMC or committers.
3) The team is questioning and objecting to the move
That sounds like a bad sign to me.
Of course, let us see if the PMC changes the opinion and would be open to
accepting fixes and releasing 1.x versions, however, it is really hard to
understand why trivial changes like "moving 1.x to git" create that many
questions and objections.
> 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
> 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)
