You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by to...@apache.org on 2022/08/28 04:53:05 UTC
[lucene] branch main updated: a bit of clarification about GitHub Milestone
This is an automated email from the ASF dual-hosted git repository.
tomoko pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/lucene.git
The following commit(s) were added to refs/heads/main by this push:
new 29f94b04040 a bit of clarification about GitHub Milestone
29f94b04040 is described below
commit 29f94b04040f94b52ef24393ff0b89476b4a403e
Author: Tomoko Uchida <to...@gmail.com>
AuthorDate: Sun Aug 28 13:52:58 2022 +0900
a bit of clarification about GitHub Milestone
---
dev-docs/github-issues-howto.md | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/dev-docs/github-issues-howto.md b/dev-docs/github-issues-howto.md
index a9a3a61fe71..c6a00358990 100644
--- a/dev-docs/github-issues-howto.md
+++ b/dev-docs/github-issues-howto.md
@@ -23,14 +23,20 @@ under the License.
We use Milestones for release planning.
-A milestone represents a release. All issues/PRs associated with a milestone must be resolved before the release, which means unresolved issues/PRs in a milestone are blockers for the release. Release managers should consider how to address blockers. Some may be resolved by developers, and others may be postponed to future releases.
+A milestone represents a release. Issues and/or PRs should be associated with proper Milestones where the changes are planned to be delivered.
-The Milestone associated with an Issue/PR should be the same version in CHANGES. For instance, if an Issue/PR appears in the CHANGES section 10.0.0, it should be marked as Milestone 10.0.0.
+All issues/PRs associated with a milestone must be resolved before the release, which means unresolved issues/PRs in a milestone are blockers for the release. Release managers should consider how to address blockers. Some may be resolved by developers, and others may be postponed to future releases.
Once the release is done, the Milestone should be closed then a new Milestone for the next release should be created.
+You can see the list of current active (opened) Milestones here. https://github.com/apache/lucene/milestones
+
See [GitHub documentation](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/about-milestones) for more details.
+### Relation between Milestones and CHANGES
+
+The Milestone associated with an Issue/PR should be the same version in [CHANGES](https://github.com/apache/lucene/blob/main/lucene/CHANGES.txt). For instance, if an Issue/PR appears in the CHANGES section 10.0.0, it should be marked as Milestone 10.0.0.
+
## Issue labels
There are a few pre-defined label families to organize/search issues.