Just in case, I proposed Milestone for version management both in the Jira
issue and dev@ mail list several times.
There were a few questions about the proposal. And few people went along
with that.
If you want to use Milestone, I'm fine with it. Please clarify that in
https://github.com/apache/lu
Hi,
instead of fix version i used the Milestone 9.4 to indicate the proposed
fix version. Why do we need a label for this?
See what I did in an issue I am working on and the corresponding PR:
https://github.com/apache/lucene/issues/11701 and
https://github.com/apache/lucene/pull/11718
Uwe
> I wonder if going forward we want to main that for new issues?
Maybe we just tag "fix-version:main"? Renaming a label (e.g.
fix-version:main -> fix-version:10.0.0) is easy when we release a major
version.
> I happened to notice there is also this "milestone" feature in github --
does that seem
Thanks! It seems to be working nicely.
Question about the fix-version: tagging. I wonder if going forward we
want to main that for new issues? I happened to notice there is also
this "milestone" feature in github -- does that seem like a place to
put version information?
On Wed, Aug 24, 2022 at 3
Issue migration has been completed (except for minor cleanups).
This is the Jira -> GitHub issue number mapping for possible future usage.
https://github.com/apache/lucene-jira-archive/blob/main/migration/mappings-data/issue-map.csv.20220823_final
GitHub issue is now fully available for all issu
