I agree; I've always used CHANGES for a quick historical view. What about the release manager use case? I haven't done a release, but I think we generally want to know if people are targeting changes for an upcoming release, especially if they are blockers. We could just use email to find out about these, but I think it's better if we can look them up in the issue db.
On Thu, Aug 25, 2022 at 9:40 AM Robert Muir <rcm...@gmail.com> wrote: > > On Thu, Aug 25, 2022 at 6:11 AM Michael Sokolov <msoko...@gmail.com> wrote: > > > > The milestone looks appealing since it is prominent and relatively easy to > > use. The only drawback I have heard is that it is single valued. It still > > seems we could use it to document the first version in which something is > > released, although it wouldn't be possible to record other releases into > > which a fix it feature is back ported. > > The fix-version stuff seems like a JIRA relic to me. there are at > least two other places to get the information. If someone wants to > know this, they can see all the commits to the branches, can check > CHANGES.txt, etc? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
