Hello all.
I guess this has been discussed before (several times). Once again, I would
propose to relax the requirement for creating JIRA account/issue when
contributing.
LUCENE-10545 <https://issues.apache.org/jira/browse/LUCENE-10545> allows
CHANGES.txt to directly mention to GitHub PR (to be exact, I just fixed the
obsoleted link to the repository) so that developers can skip opening a
JIRA if he/she is ready to start the conversation with a working PR.
To see how it will work, please see the associated PR on it - this includes
a concrete example.
Please note that this does not replace Jira with Github (we still
absolutely need issues for discussion and migrating Jira issue to GitHub
issue is out of the scope here), but provides an option for developers who
already have working patches.
Thank you,
Tomoko
I guess this has been discussed before (several times). Once again, I would
propose to relax the requirement for creating JIRA account/issue when
contributing.
LUCENE-10545 <https://issues.apache.org/jira/browse/LUCENE-10545> allows
CHANGES.txt to directly mention to GitHub PR (to be exact, I just fixed the
obsoleted link to the repository) so that developers can skip opening a
JIRA if he/she is ready to start the conversation with a working PR.
To see how it will work, please see the associated PR on it - this includes
a concrete example.
Please note that this does not replace Jira with Github (we still
absolutely need issues for discussion and migrating Jira issue to GitHub
issue is out of the scope here), but provides an option for developers who
already have working patches.
Thank you,
Tomoko