Assuming there are no strong objections, I merged the PR. This is effective from now on. In brief, a CHANGES entry can refer Jira issues or GItHub pull requests. In the latter case, Jira issue is not required or is optional (it's up to the author).
2022年4月30日(土) 12:29 Tomoko Uchida <[email protected]>: > The pull request receives one approval and a few comments. Feedback is > welcome, thank you. > > There are no effects on the current contribution workflow though, this > could slightly change the forms of communication (some people will continue > to use both Jira and GitHub as before, some people might tend to use GitHub > only). > > I am not familiar with how to proceed with such workflow changes; > according to the "lazy consensus" concept that is well described on this > page, I plan to merge it with an example CHANGES entry later next week if > there are no objections. > https://community.apache.org/committers/lazyConsensus.html > > Tomoko > > > 2022年4月29日(金) 22:01 Tomoko Uchida <[email protected]>: > >> 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 >> >
