[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464774#comment-17464774
]
Vladimir Sitnikov commented on LOG4J2-3272:
-------------------------------------------
[~rgoers], [~vy], [~rpopma],
As Chris Lambertus says in
https://issues.apache.org/jira/browse/INFRA-22654?focusedCommentId=17464771&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17464771
, in order to re-open apache/log4j repository for future development, a
decision from PMC is needed; and there's a need to confirm Git contains the
latest sources.
{quote} If they wish to continue development with Git, they would need to
confirm that the log4j GitHub mirror is current with the svn repo, then we can
make the SVN repo read-only and promote the GitHub repo to read/write.{quote}
Could you please agree and add your decision to INFRA-22654 ?
For example, you could just add a lot of PMC votes on "[VOTE] Move log4j 1.x
from SVN to Git," thread.
> 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)
