This is why I’ve suggested accepting bug reports via email in addition to GitHub. Any bug tracker we use which isn’t hosted by Apache will likely have similar issues.
> On Nov 7, 2022, at 8:58 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > Just FYI, > > There is a release note discussion going on on the Maven list and someone > said the following when I mentioned our plan to switch to GitHub Issues: > > "So you mean using ONLY gh for issues? > So by doing this, you will exclude people living in countries banned > from Github. > Is it acceptable from an Apache Foundation POV?" > > Gary > > On Mon, Nov 7, 2022, 16:03 Volkan Yazıcı <vol...@yazi.ci> wrote: > >> In the context of migrating away from JIRA to GitHub Issues, I want to >> replace the current maven-changes-plugin setup with a merge-conflict-free >> Markdown-based solution. I have elaborated the details in LOG4J2-3628 >> <https://issues.apache.org/jira/browse/LOG4J2-3628>. >> >> Since this will change the behaviour of how we introduce changes and make >> releases, I would appreciate it if committers could skim through it and >> share their feedback. >>
