Re: [ANNOUNCE] Issue migration Jira to GitHub starts on Monday, August 22

It looks great, thank you for this monumental effort, Tomoko. Dawid On Wed, Aug 24, 2022 at 9:19 PM Tomoko Uchida wrote: > > > > Issue migration has been completed (except for minor cleanups). > This is the Jira -> GitHub issue number mapping for possible future usage. >

Re: Label vs. Milestone for version management?

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

Re: [ANNOUNCE] Issue migration Jira to GitHub starts on Monday, August 22

Thank you Tomoko! It looks AWESOME! I will work on fixing jirasearch to index from GitHub ... Mike On Thu, Aug 25, 2022 at 4:32 AM Vigya Sharma wrote: > Love this! Thanks for all the hard work, Tomoko. > - > Vigya > > > On Wed, Aug 24, 2022 at 12:27 PM Michael Sokolov > wrote: > >> Thanks!

Re: Label vs. Milestone for version management?

On Thu, Aug 25, 2022 at 6:11 AM Michael Sokolov 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 >

Re: Label vs. Milestone for version management?

For now, please use Label "fix-version:x.x.x" for version management as written in https://github.com/apache/lucene/blob/main/dev-docs/github-issues-howto.md. In other words, 1. Use fix-version:10.0 for main branch.

Label vs. Milestone for version management?

Hi all. I once proposed using Milestone for version management in GitHub before the issue migration. The proposal did not gain any support, so I thought we concluded that we use "fix-version" Label for issue/PR version management. But it looks like there are suggestions to use Milestone. What

Re: [ANNOUNCE] Issue migration Jira to GitHub starts on Monday, August 22

Love this! Thanks for all the hard work, Tomoko. - Vigya On Wed, Aug 24, 2022 at 12:27 PM Michael Sokolov wrote: > 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

Re: Label vs. Milestone for version management?

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

Re: Label vs. Milestone for version management?

So the Solr Operator has been using Github Issues for a few releases now, and the Milestone feature has worked really well for a blockers list. I agree that it should not be the canonical list of things that were included in that release (although it will likely be very close), but it is very

Re: [ANNOUNCE] Issue migration Jira to GitHub starts on Monday, August 22

Hi Tomoko! Great and works well! I also tested backporting with cherry-picks on issue https://github.com/apache/lucene/issues/11701: - The linked PR (https://github.com/apache/lucene/pull/11718) was main only. In the squash merge message I added "This fixes #11701." - After merging the PR

Re: Label vs. Milestone for version management?

Tomoko - sorry to re-raise this when we thought it had been settled. Having never really used github issues, I don't think I fully understood the arguments there. On Thu, Aug 25, 2022 at 3:50 AM Tomoko Uchida wrote: > > Hi all. > > I once proposed using Milestone for version management in GitHub

Re: Label vs. Milestone for version management?

Hi, In addition, once you have done a release, you can close the milestone with the date of release and this would mark all those issues as "delivered". So quick filters won't show them anymore. And for the RM it is great to get a list of issues form the Milestones page. If you also use the

Re: Label vs. Milestone for version management?

On Thu, Aug 25, 2022 at 9:47 AM Michael Sokolov wrote: > > 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,

Re: Label vs. Milestone for version management?

About the milestones being single-valued - we already have this single-value notion in changes.txt, don't we? We add a note about the issue to the "last" branch an issue was backported to. I agree sometimes it could be more complicated (vide openjdk, where issues are backported selectively to a

Re: [JENKINS-EA] Lucene-main-Linux (64bit/jdk-19-ea+32) - Build # 36603 - Failure!

This one again: # SIGSEGV (0xb) at pc=0x7ff8eb125163, pid=2754499, tid=2755109 # # JRE version: OpenJDK Runtime Environment (19.0+32) (build 19-ea+32-2220) # Java VM: OpenJDK 64-Bit Server VM (19-ea+32-2220, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc,

Re: [ANNOUNCE] Issue migration Jira to GitHub starts on Monday, August 22

Hi Uwe, thanks for testing. > But now my question: To contact the original bug submitter I acnt do > anything in JIRA anymore. That's fine, but when do we add the automated > message to all issues with a reference to the new Github URL? This would > help to inform the user like "now look here