I agree that "discussion" will be done on mailing lists (as always).
Properly speaking, stopping using Jira means "we don't accept patch style
contributions anymore".
GitHub doesn't allow ".patch" files as attachments; it'd be reasonable for
GitHub.
I think we'd still have the mailing lists open for discussion. So anyone
not willing or able to use GitHub would still be able to participate in a
meaningful way. Having two parallel bug trackers seems much less useful to
me. I'd rather have people emailing to a list that is active rather than
Thank you Mike for opening the discussion.
I don't really have a clear "opinion" on that, but I just wanted to try to
explain my perspective.
Today almost all development is already going on GitHub pull requests, then
it would be a natural direction for the majority of devs to move our
primary
Hi Team,
Thanks to Tomoko's amazing hard work (
https://github.com/apache/lucene-jira-archive), we are getting close to
having strong tooling and a solid plan to migrate all past Jira issues to
GItHub issues!
But one contentious point is whether to leave Jira read-only or read-write
after the
