[
https://issues.apache.org/jira/browse/LOG4J2-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916505#comment-17916505
]
Philippe Cloutier commented on LOG4J2-3692:
-------------------------------------------
Thank you very much Piotr
To clarify, Apache is trying to move Log4j's issue tracking from Jira to
GitHub, but existing tickets are not migrated.
GitHub has been developing its ITS engine for more than a decade by now, and it
is still nowhere close to Jira. I for one seriously doubt it will ever get
there. I'm afraid migrating a project as important and mature as Log4j to
GitHub will never succeed. I recommend giving up.
> Log4j moved to GitHub Issues
> ----------------------------
>
> Key: LOG4J2-3692
> URL: https://issues.apache.org/jira/browse/LOG4J2-3692
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Piotr Karwasz
> Priority: Blocker
>
> Apache Log4j moved to [GitHub
> Issues|https://github.com/apache/logging-log4j2/issues].
> We only use JIRA as an archive of old issues. If you submit a new JIRA issue,
> it is unlikely to be addressed.
> See INFRA-26319
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
