Re: Allow to directly link to GitHub PR from CHANGES?

> Just for a supplement, this is effective for all developers (committers, long-term or first-time contributors) and all pull requests, without any conditions. I'm sorry for being verbose for it again, but I'd like to emphasize this point. I mean, if we absolve only first-time contributors from

Re: Allow to directly link to GitHub PR from CHANGES?

Thank you Adrien for confirming. Just for a supplement, this is effective for all developers (committers, long-term or first-time contributors) and all pull requests, without any conditions. Every developer can skip opening a JIRA when contributing if he/she feels it's an unnecessary extra

Re: Allow to directly link to GitHub PR from CHANGES?

Thanks Tomoko! I'm +1 on no longer requiring external contributors to create JIRA issues, JIRA can be quite intimidating the first time you have to deal with it with its complex UI, specific markup language, etc. This will hopefully improve the experience of first-time contributors. On Mon, May

Re: Allow to directly link to GitHub PR from CHANGES?

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 : > The

Re: Allow to directly link to GitHub PR from CHANGES?

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

Allow to directly link to GitHub PR from CHANGES?

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 allows CHANGES.txt to directly mention to GitHub PR (to be