Hi all.
Now we fully support GItHub issues, you can mention Issue numbers as well
as PR numbers in lucene/CHANGES.txt
<https://github.com/apache/lucene/blob/main/lucene/CHANGES.txt>.
You can mention both issues and PRs in CHANGES.txt by GITHUB#NN. NN is
either an issue number or a PR number.
From a broader viewpoint, there are no differences between issues and pull
requests. You can associate both issues and PRs with Milestones/Labels and
mention both issues and PRs in the CHANGES in the very same manner.
Sometimes a pull request would be sufficient, and sometimes you may want to
open an issue and PRs on it, depending on the context. [1]
[1]
https://github.com/apache/lucene/blob/main/dev-docs/github-issues-howto.md#should-i-raise-an-issue-when-i-already-have-a-working-patch
Tomoko
Now we fully support GItHub issues, you can mention Issue numbers as well
as PR numbers in lucene/CHANGES.txt
<https://github.com/apache/lucene/blob/main/lucene/CHANGES.txt>.
You can mention both issues and PRs in CHANGES.txt by GITHUB#NN. NN is
either an issue number or a PR number.
From a broader viewpoint, there are no differences between issues and pull
requests. You can associate both issues and PRs with Milestones/Labels and
mention both issues and PRs in the CHANGES in the very same manner.
Sometimes a pull request would be sufficient, and sometimes you may want to
open an issue and PRs on it, depending on the context. [1]
[1]
https://github.com/apache/lucene/blob/main/dev-docs/github-issues-howto.md#should-i-raise-an-issue-when-i-already-have-a-working-patch
Tomoko