Hi devs,
We use Milestone for release planning in GitHub instead of issue labels.
The change was suggested/discussed in a recent mail thread [1].
In short,
1. Use Milestone for release planning. An issue/PR can have only one
Milestone.
2. Do not use JIra-style "fix-versoin" label.
If an
> This works well, but we should maybe change the CHANGES.txt perl script
to always link using the URL pattern "/issue/" instead of "/pull/". I think
"issue" is the more generic term (I see PR as a special case of issue).
Yes, the path should be "/issue". I'll make the change.
Tomoko
Hi Tomoko,
I also tested that the links in CHANGES.txt also work with issues. That
is confirmed. Baysically for Github there's an automatic redirect if you
link to an ID as PR and in reality it is an issue:
E.g.,
I opened a PR to propose Milestone for release planning.
https://github.com/apache/lucene/pull/11723
Version management is one of the most important things for an
issue-tracking system. Is this clear to everyone?
```
## Milestones
We use Milestones for release planning.
A milestone represents
Hi,
it looks like many people favor Milestone over Label? Then I would like to
bring my proposal utilizing Milestone for version management up again.
A draft plan in my mind:
- A Milestone represents a release. E.g. Milestone 9.4.0 includes all
changes in version 9.4.0.
- Associate issues/PRs to
