Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

clarify the relation between CHANGES and Milestone

This commit is contained in:
Tomoko Uchida 2022-08-27 12:58:33 +09:00
parent 224953304c
commit 09a7f9aa53
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
dev-docs/github-issues-howto.md
View File

@ -25,6 +25,8 @@ 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.
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.
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.