Re: Fix version / milestones

A naive solution to enforce Milestone for every pull request would be to fail Github CI if no milestone is set for that. on: pull_request: branches: - main types: [synchronize, opened, reopened, milestoned, demilestoned] jobs: check-milestone: name: Check Milestone

Re: Subject: New branch and feature freeze for Lucene 9.4.0

> Branch branch_9_4 has been cut and versions updated to 9.5 on stable branch. Then the GitHub Milestone for 9.5 also needs to be created. This time, I created Milestone 9.5.0. We should include it in the release process. https://github.com/apache/lucene/milestone/4 2022年9月3日(土) 4:42 Michael

Re: Lucene 9.4.0 release

nes, and everything should be fairly straightforward. If you need any help, I'd be happy to review the necessary updates on the release wizard tool. I have little time to make a patch for that myself right now, sorry. Tomoko 2022年9月1日(木) 10:02 Tomoko Uchida : > > One thing is that for JI

Re: Lucene 9.4.0 release

y >>> all the developers. And I confess I didn't know about that nice >>> milestone view! It makes this very easy, assuming of course that >>> everyone follows the guidelines and labels the issues with the >>> milestone. >>> >>> On Wed, Aug 31, 2022 at 11

Re: Lucene 9.4.0 release

ines and labels the issues with the > milestone. > > On Wed, Aug 31, 2022 at 11:16 AM Tomoko Uchida > wrote: > > > > Ok in short, you can find blockers for 9.4.0 here. > > https://github.com/apache/lucene/milestone/3 > > > > If there are other issues/PRs

Re: Lucene 9.4.0 release

Ok in short, you can find blockers for 9.4.0 here. https://github.com/apache/lucene/milestone/3 If there are other issues/PRs that are still not resolved but planned to be delivered in 9.4.0, just set their Milestone as 9.4.0. Then they will appear in the list. 2022年9月1日(木) 0:00 Tomoko Uchida

Re: Lucene 9.4.0 release

I believe we decided to use GitHub Milestone for release planning and I wrote documentation about it. https://github.com/apache/lucene/blob/main/dev-docs/github-issues-howto.md Is this unclear to you? 2022年8月31日(水) 23:13 Michael Sokolov : > Hi, I'd like to start the ball rolling for a 9.4.0

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

well done. > > Given how many difficult aspects there were on the way, you can probably > offer jira-github transition services and make them your business! :) > > Dawid > > On Mon, Aug 29, 2022 at 1:22 PM Tomoko Uchida < > tomoko.uchida.1...@gmail.com> wrote: > &

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

gt; a possible discussion also for closed issues proceeds. > > Uwe > > Am 28. August 2022 13:03:53 MESZ schrieb Tomoko Uchida < > tomoko.uchida.1...@gmail.com>: >> >> >> >> Jira notification to issues@ was stopped. >> I'm going to run the scrip

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

ssue was moved to GitHub. It's Sunday. Convenient for me to run the script that can send lots of emails (to people who are involved in Jira issues.) Tomoko 2022年8月26日(金) 23:06 Tomoko Uchida : > > This works well, but we should maybe change the CHANGES.txt perl script > to always link

Clarification about mentions in CHANGES

Hi all. Now we fully support GItHub issues, you can mention Issue numbers as well as PR numbers in lucene/CHANGES.txt . You can mention both issues and PRs in CHANGES.txt by GITHUB#NN. NN is either an issue number or a PR number.

To committers: Use Milestones for release planning

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

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

ead of "/pull/". I think > "issue" is the more generic term (I see PR as a special case of issue). > > The PR to change this would be a one-liner. > > Uwe > > Am 26.08.2022 um 04:09 schrieb Tomoko Uchida: > > Hi Uwe, > thanks for testing. > &g

Re: Label vs. Milestone for version management?

to future releases. Once the release is done, the Milestone should be closed then a new Milestone for the next release should be created. ``` Tomoko 2022年8月26日(金) 19:03 Tomoko Uchida : > Hi, > it looks like many people favor Milestone over Label? Then I would like to > bring my proposal

Re: Label vs. Milestone for version management?

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

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

ut 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 user looks github and > sees: issue resolved". > > Uwe > > Am 25.08.2022 um 13:04 schrieb Dawid Weiss:

Re: Label vs. Milestone for version management?

less we gain consensus on introducing it. Feel free to push it forward if you would like, please. Tomoko 2022年8月25日(木) 16:47 Tomoko Uchida : > Hi all. > > I once proposed using Milestone for version management in GitHub before > the issue migration. > The proposal did not gain any suppo

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

the issues. >> - Pull requests are not affected. You can open/update PRs as usual. >> Please let me know if you have any trouble with PRs. >> >> >> Tomoko >> >> >> 2022年8月18日(木) 18:23 Tomoko Uchida : >> >>> Hello all, >>> >&

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

/issues/1072 - While you cannot break these issues, migration scripts can modify/overwrite your comments on the issues. - Pull requests are not affected. You can open/update PRs as usual. Please let me know if you have any trouble with PRs. Tomoko 2022年8月18日(木) 18:23 Tomoko Uchida : > He

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

Hello all, The Lucene project decided to move our issue tracking system from Jira to GitHub and migrate all Jira issues to GitHub. We start issue migration on Monday, August 22 at 8:00 UTC. 1) We make Jira read-only before migration. You cannot update existing issues until the migration is

Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

Thanks Elliot, added: https://github.com/apache/lucene-jira-archive/commit/6baddb9bb7fd0cacf39eda8409cc24758ec87722 2022年8月16日(火) 9:00 Elliot Lin : > elelliot,elliotzlin,Elliot Lin > > On Mon, Aug 15, 2022 at 4:02 AM Marios Trivyzas wrote: > >> Many thanks! >> >> On Mon, Aug 15, 2022 at 2:00

The way to silence Jira notifications?

Hi, I wonder if perhaps there is anyone who knows the way to completely silence Jira notifications (during issue migration). I see the notification settings in Lucene Jira but can't really test it. Thanks, Tomoko

Re: [HELP] Please spot-check the migrated Lucene GitHub issues!

'm a bit surprised that the attachment would have > disappeared > > On Tue, Aug 9, 2022 at 6:56 AM Uwe Schindler wrote: > > > > Hi Tomoko, > > > > this looks all great! Go ahead and thanks for taking care. I will follow > the INFRA issue during my vacation. > > >

Re: [HELP] Please spot-check the migrated Lucene GitHub issues!

McCandless > > http://blog.mikemccandless.com > > > On Mon, Aug 8, 2022 at 11:43 AM Tomoko Uchida < > tomoko.uchida.1...@gmail.com> wrote: > >> Hi, >> this is the latest iteration of the migrations test. >> https://github.com/mocobeta/forks-migration-test-2

Re: [HELP] Please spot-check the migrated Lucene GitHub issues!

t 8:47 PM Tomoko Uchida < > tomoko.uchida.1...@gmail.com> wrote: > > > Is it intentional that we do not set Assignees on migration? >> >> You can assign a GitHub account only when it has push access to the >> repository; it was infeasible to give push acces

Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

) 14:41 Aditya Varun Chadha : > Thanks Tomoko, > There is no activity in JIRA from me as far as I can recall. This is the > correct and only account though. > > On Sun 7. Aug 2022 at 05:50, Tomoko Uchida > wrote: > > > Hi Aditya, > > I found a Jira user "adich

Make both Jira and GitHub issues/PRs read-only during issue migration

Hi everyone. This is an announcement for a change in the coming migration for our issue system. I first thought we'd keep our issue system available during migration (and made a plan not to introduce downtime). However, there are a couple of suggestions and discussions in an issue

Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

ote: > > > jira: gnewton > > github: gnewton (github.com/gnewton) > > > > Thanks, > > Glen > > > > > > > > On Sat, 6 Aug 2022 at 14:11, Tomoko Uchida > > > wrote: > > > > > Hi everyone. > > > > > > I wanted

Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

> > > > On Sat, 6 Aug 2022 at 14:11, Tomoko Uchida > wrote: > > > Hi everyone. > > > > I wanted to let you know that we'll extend the deadline until the date > the > > migration is started (the date is not fixed yet). > > Please let us know y

Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

Hi everyone. I wanted to let you know that we'll extend the deadline until the date the migration is started (the date is not fixed yet). Please let us know your Jira/Github usernames if you don't see mapping(s) for your account in this file:

***UNCHECKED*** Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

Hi Rushabh. Thanks, I added a mapping for your accounts: https://github.com/apache/lucene-jira-archive/commit/6f9501ec68792c1b287e93770f7a9dfd351b86fb Tomoko 2022年8月5日(金) 8:02 Rushabh Shah : > Hi, > My mapping is: > JiraName,GitHubAccount,JiraDispName > shahrs87, shahrs87, Rushabh Shah > >

Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

Hi Atri and Christian, thanks for your reply, we already have your accounts in - https://github.com/apache/lucene-jira-archive/blob/7654c0168a86fb05e942666d4514d48966d223bb/migration/mappings-data/account-map.csv.20220722.verified#L42 -

Re: [HELP] Link your Apache Lucene Jira and GitHub account ids before Thursday August 4 midnight (in your local time)

Hi Mike, Marcus, and Praveen: I verified the added two mappings - these Jira users have activity on Lucene Jira, also corresponding GitHub accounts are valid. - marcussorealheis - pru30 Tomoko 2022年8月1日(月) 18:40 Michael McCandless : > Thanks Praveen, > > I added your mapping here: >

Re: [HELP] Please spot-check the migrated Lucene GitHub issues!

> Is it intentional that we do not set Assignees on migration? You can assign a GitHub account only when it has push access to the repository; it was infeasible to give push access to all committers to the test repo (an invite/accept flow is needed for each committer). Assignees will be set when

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

my GitHub account. A bit awkward, but it'd be an acceptable workaround I think. Tomoko 2022年7月19日(火) 23:24 Tomoko Uchida : > > I think missing a few updates would be preferable to having 10k > messages. Just my opinion though. > I don't have objections. Then let's disable Jira n

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

ons? 2022年7月19日(火) 23:17 Houston Putman : > I think missing a few updates would be preferable to having 10k messages. > Just my opinion though. > > On Tue, Jul 19, 2022 at 10:11 AM Tomoko Uchida < > tomoko.uchida.1...@gmail.com> wrote: > >> > 1. Make Jira read only >

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

> I plan a rehearsal that migrates whole existing issues into a test repo next week. Could some people help/test it (randomly open/close issues, add comments, etc. while the migration script is running)? It'd be done by an agent program - I'll draft it. 2022年7月19日(火) 23:10 Tomoko Uch

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

the migration). 2022年7月19日(火) 23:05 Tomoko Uchida : > > 2. Send a message to dev@ stating new issues should now be opened in > github > > 3. Start the migration > > Maybe we can do a simulation for this. > I plan a rehearsal that migrates whole existing issues into a test re

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

mments, etc. while the migration script is running)? 2022年7月19日(火) 22:47 Tomoko Uchida : > > 1. Make Jira read only > > At the very last step, we'll add comments saying "This was moved GitHub > " to each Jira issue. It has to be done after the migration was > complet

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

hread is there would be no downtime for new issues. > > On Tue, Jul 19, 2022 at 00:07 Tomoko Uchida > wrote: > >> OK, thank you everyone for your comments/suggestions. >> I will ask infra to make Lucene Jira read-only after the migration is >> completed (if there are n

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

OK, thank you everyone for your comments/suggestions. I will ask infra to make Lucene Jira read-only after the migration is completed (if there are no explicit objections). For people who are critically affected by this change, please let me know about your inconvenience. I'll try to find

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

Candless > > http://blog.mikemccandless.com > > > On Mon, Jul 18, 2022 at 12:41 AM Tomoko Uchida < > tomoko.uchida.1...@gmail.com> wrote: > >> I agree that "discussion" will be done on mailing lists (as always). >> Properly speaking, stoppin

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

ments to a repository that we may very likely start to ignore. > > On Sun, Jul 17, 2022, 10:09 AM Tomoko Uchida > wrote: > >> Thank you Mike for opening the discussion. >> >> I don't really have a clear "opinion" on that, but I just wanted to try >> to

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

Thank you Mike for opening the discussion. I don't really have a clear "opinion" on that, but I just wanted to try to explain my perspective. Today almost all development is already going on GitHub pull requests, then it would be a natural direction for the majority of devs to move our primary

Re: A prototype migration tool Jira to GitHub

it history), moreover, it may not so exciting to work on - therefore I would really appreciate your help. Thanks, Tomoko 2022年7月1日(金) 16:53 Tomoko Uchida : > It seems there are no major objections? > > A status update - we now have a public ASF repository for the migration > and all w

Call for public comments on Which GitHub accont we should/can use for migration

Hello all. This is the last thing (to me) we would need a consensus on the GitHub issue migration. The problem is, that we cannot preserve the original Jira issue/comment authors since GitHub API assumes the caller's account is the author and does not allow callers to change it by any means. I

Re: A prototype migration tool Jira to GitHub

e list): > > https://github.com/mocobeta/sandbox-lucene-10557/issues/10838#issuecomment-1166777318 > > 2) inline images in the description point at nothing. > > But it's already quite impressive. > > Dawid > > On Tue, Jun 28, 2022 at 6:49 PM Tomoko Uchida > wrote:

Re: [GitHub] [lucene-jira-archive] mocobeta opened a new issue, #1: Fix markup conversion error

. 2022年6月29日(水) 20:23 Tomoko Uchida : > I set https://github.com/apache/lucene-jira-archive/blob/main/.asf.yaml > to send all notifications to my ASF address, but this did not help... > > > > > 2022年6月29日(水) 19:24 Tomoko Uchida : > >> Sorry, it seems the all updates i

Re: [GitHub] [lucene-jira-archive] mocobeta opened a new issue, #1: Fix markup conversion error

I set https://github.com/apache/lucene-jira-archive/blob/main/.asf.yaml to send all notifications to my ASF address, but this did not help... 2022年6月29日(水) 19:24 Tomoko Uchida : > Sorry, it seems the all updates in > https://github.com/apache/lucene-jira-archive are noticed in dev@ lis

Re: [GitHub] [lucene-jira-archive] mocobeta opened a new issue, #1: Fix markup conversion error

Sorry, it seems the all updates in https://github.com/apache/lucene-jira-archive are noticed in dev@ list. I don't see the configuration/setting for the repository. Could anyone mute this? Tomoko 2022年6月29日(水) 19:06 GitBox : > > mocobeta opened a new issue, #1: > URL:

Re: A prototype migration tool Jira to GitHub

rototyping and if there are next iterations, these will be rehearsals for the actual migration. Tomoko 2022年6月27日(月) 10:27 Tomoko Uchida : > > It looks like the GitHub Danger Zone can transfer a repository? > > "Transferring a repository" creates another repository different

Re: Plan for GitHub issue metadata management

questions on it; then I'd keep the current operation: multiple fix versions. 2022年6月20日(月) 19:10 Tomoko Uchida : > > I haven't used the "project" feature either - maybe it could be an > option but I can't have an opinion on it. Is there anyone who has > experience with i

Re: A prototype migration tool Jira to GitHub

sitories/creating-and-managing-repositories/transferring-a-repository > > Mike McCandless > > http://blog.mikemccandless.com > > > On Sun, Jun 26, 2022 at 6:40 PM Tomoko Uchida < > tomoko.uchida.1...@gmail.com> wrote: > >> >> >> >> >>&

Re: A prototype migration tool Jira to GitHub

ence between "Jira to GitHub" and "GitHub to GitHub". > >> On Sat, Jun 25, 2022 at 7:53 AM Tomoko Uchida >> wrote: >> > >> > I may have to share another practical consideration on the migration >> that I haven't mentioned yet. >&g

Re: A prototype migration tool Jira to GitHub

sfers all issues from one repo to another repo. > On Sat, Jun 25, 2022 at 7:53 AM Tomoko Uchida > wrote: > > > > I may have to share another practical consideration on the migration > that I haven't mentioned yet. > > > > We are not allowed to have admin ac

Re: A prototype migration tool Jira to GitHub

to find someone who is willing to take over the job. 2022年6月25日(土) 19:19 Tomoko Uchida : > Hi Dawid, > > > Emm.. sorry for being slow - what is it that you want me to do? :) > Unwatch->Ignore? > > I'm sorry for being ambiguous. Could you set your notification set

Re: A prototype migration tool Jira to GitHub

Hi Dawid, > Emm.. sorry for being slow - what is it that you want me to do? :) Unwatch->Ignore? I'm sorry for being ambiguous. Could you set your notification setting on the repository as "Participating and @mentions"? In the testing of migration scripts, I will import many fake issues where

Re: A prototype migration tool Jira to GitHub

Hi Houston and Dawid, Thanks so much for your help. I might use other test repos but when I try to migrate a large portion of issues I post them to https://github.com/mocobeta/sandbox-lucene-10557. > So did I. There are two ways to receive notifications as you know, 1) watch all activities and

Re: A prototype migration tool Jira to GitHub

with my account, just wanted to test it with other one or two accounts. Tomoko 2022年6月24日(金) 21:12 Adrien Grand : > FWIW I don't mind receiving these one-time notifications for the purpose > of the migration. > > On Fri, Jun 24, 2022 at 12:58 PM Tomoko Uchida < > tomoko.uchida.1.

Re: A prototype migration tool Jira to GitHub

a sane decision to me. 2022年6月24日(金) 16:18 Uwe Schindler : > > Hi, > > Am 23.06.2022 um 19:09 schrieb Tomoko Uchida: > > uschindler,Uwe Schindler,2474 > > If you could give me some "example mail", I can add a "feed to trash" sieve > rule b

Re: A prototype migration tool Jira to GitHub

take 7-8 hours I think. Tomoko 2022年6月24日(金) 0:39 Tomoko Uchida : > It seems not new - I don't figure out why this is not published as a > public API yet but according to the comments there, it could be > buggy/unstable (still worth a try to me). > > > > 2022年6月24日(金) 0:

Re: A prototype migration tool Jira to GitHub

It seems not new - I don't figure out why this is not published as a public API yet but according to the comments there, it could be buggy/unstable (still worth a try to me). 2022年6月24日(金) 0:26 Tomoko Uchida : > I just browsed through this article about the "import issues" API (l

Re: A prototype migration tool Jira to GitHub

triggering notifications. I'll try it later; thank you Rob for providing the information. 2022年6月23日(木) 23:18 Michael Sokolov : > oh phew! glad to hear this was expected > > On Thu, Jun 23, 2022 at 10:17 AM Tomoko Uchida > wrote: > > > > > Many comments were lost in t

Re: A prototype migration tool Jira to GitHub

o 2022年6月23日(木) 23:09 Tomoko Uchida : > Hi, > I have little now to carefully read/respond to all replies right now, but > just wanted to answer this. > > > Will it be possible to preserve links from issues -> pull requests? > > Yes it's a bit cumbersome (and it coul

Re: A prototype migration tool Jira to GitHub

ghts: >>> > >>> > * I don’t think a flood of notifications from the import is a problem. >>> It’s a one time hassle, and having the actual user links is nice for >>> GitHub’s cross linking system. >>> > >>> > * Do you have an estimate

A prototype migration tool Jira to GitHub

Hi all, again - this is about GitHub migration. We have a large disagreement on whether we should migrate existing Jira issues (including all closed issues) to GitHub or not. I drafted a tiny migration tool [1] to see how it looks if we move Jira issues to GitHub, and tried to migrate a small

Accidental mentions on GitHub (relates to LUCENE-10557)

Hi, I think there are people who received GitHub mentions from the test repository for LUCENE-10557. Apologies for the noise, it was accidental. I'll convert all mentions in existing jira issues not to send mentions to anyone when testing migration scripts. Tomoko

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

Thanks for your suggestions; actually ASF should have information on the account mapping. For now, I'll just prepare scripts to embed the mapped github accounts next to the jira author/assignee name; we could ask infra or create the mapping on our own by inference if we find it's worthwhile to

Re: Plan for GitHub issue metadata management

I haven't used the "project" feature either - maybe it could be an option but I can't have an opinion on it. Is there anyone who has experience with it and wants to lead us to use it? Tomoko 2022年6月20日(月) 18:59 Jens Wille : > > Hi, > > I'm just a bystander here. But are you aware that the new

Re: Plan for GitHub issue metadata management

of these sometimes? E.g. a bug > fix may go into "8.1", "9.x" and "main"? Is it OK if we just drop support for > this? > > On Mon, Jun 20, 2022 at 12:33 PM Tomoko Uchida > wrote: >> >> Hello all. >> >> Besides whether the migration of

Plan for GitHub issue metadata management

Hello all. Besides whether the migration of existing issues should be done or not (we still do not reach an agreement on it), I started to play around with GitHub issue metadata with a test repository. The current migration plan in my mind: * Issue Type -> Supported with labels (e.g.

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

e+repo%3Aapache%2Flucene-solr+wizard+ > > Jan > > 18. jun. 2022 kl. 21:48 skrev Robert Muir : > > > > On Sat, Jun 18, 2022, 7:42 AM Tomoko Uchida > wrote: >> >> User id mapping is an important consideration for me. >> >> Can we find a mapping from

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

jects dealt with that. > > > > Perhaps a way to do it incrementally would be to create a json/xml > > (structured) dump of jira content and then write a converter into a similar > > json/xml dump for importing into github. I remember it took many iterations > > and tria

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

these script(s) in the open > then perhaps indeed we could try to collaborate and see what can be done. > > Dawid > > On Sat, Jun 18, 2022 at 5:33 AM Tomoko Uchida > wrote: >> >> Replying to myself - Jira issues can be read via REST API without any >> access token

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

prototype to me. I will be back here with a sandbox github repo where part of existing jira issues are migrated (with the best effort). In the process, we could simultaneously figure out the way to operate GitHub metadata (milestones/labels). Tomoko 2022年6月18日(土) 10:41 Tomoko Uchida : > >

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

Does anyone have information on API access keys to Jira (preferably, read-only and limited to Lucene project)? https://issues.apache.org/jira/browse/LUCENE-10622 2022年6月18日(土) 10:11 Tomoko Uchida : > > I feel like we should delay the decision on the mingration of existing > issues unti

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

a decision upon the concrete knowledge and information. Tomoko 2022年6月18日(土) 9:26 Tomoko Uchida : > > I don't intend to neglect histories in Jira... it's an important, > valuable asset for all of us and possible contributors in the future. > > It's important, *therefore*, I don

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

I don't intend to neglect histories in Jira... it's an important, valuable asset for all of us and possible contributors in the future. It's important, *therefore*, I don't want to have the degraded copies of them on GitHub. We cannot preserve all of history - again, there should be tons of

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

> I see you already have a start at the migration plan, yay! (The comment on > LUCENE-10557) > Could we maybe pull that out into a wiki page so we can more easily > collaborate on the steps? There would not be so many topics that are controversial except for the current discussion about

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

avidwsmiley > > > On Wed, Jun 15, 2022 at 4:18 PM Tomoko Uchida > wrote: >> >> It looks like we talked about two or three things at the same time - >> and I'm afraid the discussion will quickly turn into a disordered >> state and I won't be able to track it. &

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

It looks like we talked about two or three things at the same time - and I'm afraid the discussion will quickly turn into a disordered state and I won't be able to track it. Let me decide one thing: Let's NOT try to move histories to GitHub. Closed issues will remain in Jira forever and we can

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

the conversation open until we can make a decision. Tomoko 2022年6月16日(木) 0:56 Michael McCandless : > > On Wed, Jun 15, 2022 at 10:46 AM Tomoko Uchida > wrote: >> >> Thank you everyone for your suggestions. >> I don't have a strong opinion on how to handle existing issues

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

Thank you everyone for your suggestions. I don't have a strong opinion on how to handle existing issues, I just want to proceed with the migration smoothly. I'd open this discussion until we find a better (not perfect) option or reach some level of agreement. > make the Jira project read only.

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

patience. Tomoko 2022年6月14日(火) 16:41 Tomoko Uchida : > > It's been >7d since the vote was initiated and the result is: > > +1 16 (12 binding) > +0 3 (3 binding) > -1 3 (3 binding) > > This vote has PASSED. > > Thanks to everyone who is involved in the discussion and/o

[RESULT] [VOTE] Migration to GitHub issue from Jira

It's been >7d since the vote was initiated and the result is: +1 16 (12 binding) +0 3 (3 binding) -1 3 (3 binding) This vote has PASSED. Thanks to everyone who is involved in the discussion and/or voted. The work will continue on LUCENE-10557. Best, Tomoko

Re: [JENKINS] Lucene » Lucene-Check-main - Build # 5746 - Failure!

://ci-builds.apache.org/job/Solr/job/lucene-solr-1-gradle-cache-cleanup > >> job since a similar error was seen a few months ago: > >> > >> https://lists.apache.org/thread/jor6ct8l2vpq7x98hxdfn8xnp0ln6xqj > >> > >> It did fix the problem, but was never able to

Re: [VOTE] Migration to GitHub issue from Jira (LUCENE-10557)

'll cancel this vote regardless of the result. Thanks, Tomoko 2022年6月7日(火) 12:03 Tomoko Uchida : > > Hi all, > this vote received 13 ballots in total (including +1, +0, and -1) so > far, this does not reach the quorum of 15. I'll extend the term to > 2022-06-06 16:00 UTC. >

Re: [VOTE] Migration to GitHub issue from Jira (LUCENE-10557)

t;>> effort! >>>>> >>>>> Best, >>>>> Zach >>>>> >>>>> On May 30, 2022, at 2:56 PM, Houston Putman wrote: >>>>> >>>>>  >>>>> +1 Approve (PMC) >>>>> >>>

Re: [JENKINS] Lucene » Lucene-Check-main - Build # 5746 - Failure!

n a few months ago: >> >> https://lists.apache.org/thread/jor6ct8l2vpq7x98hxdfn8xnp0ln6xqj >> >> It did fix the problem, but was never able to identify the root cause. >> >> Kevin Risden >> >> >> On Mon, Jun 6, 2022 at 9:56 AM Tomoko Uchida >> wrote: >

Re: [JENKINS] Lucene » Lucene-Check-main - Build # 5746 - Failure!

I was able to log in to the ASF Jenkins Console and created this job that just deletes the whole gradle cache folder on nodes that are labeled "lucene" (please see the job configuration). https://ci-builds.apache.org/job/Lucene/job/Clean%20up%20Gradle%20cache/ I didn't set a schedule for the job

Re: module not found error in intellij

teraction with modules > > On Thu, Jun 2, 2022 at 11:36 AM Tomoko Uchida > wrote: > > > > Yes I agree with there may be bugs (I couldn't find the corresponding > > issue in IDEA's issue tracker), they are just not our bugs... > > > > > > 2022年6月3日(金) 0:17 Michael S

Re: module not found error in intellij

specially for debugging, but also for > visualizing coverage. I think there must be a bug; we do say: > > 11:15 $ ./gradlew helpIDEs > > > Task :helpIDEs > > IntelliJ IDEA > = > > Importing the project as a gradle project should just run out of the box. > &g

Re: module not found error in intellij

Hi Mike, I also can't run the tests in lucene/core.tests with IntelliJ IDEA, but it should be able to run with the plain gradle command from a console. ./gradlew -p lucene/core.tests/ test I'm not sure the exact cause of that though IDEs' java module support looks far from perfect for now, I

Re: Lucene 9.2 release

Hi all, Just a minor heads-up. We will have a more fine-grained Java version check when starting gradlew command shortly. After PR #941 is merged into main, you need newer Java (17.0.3) for a build. 2022年5月18日(水) 19:00 Tomoko Uchida : > > Hi, I just wanted to note that I opened LUCENE

Re: Welcome Lu Xugang as Lucene committer

Congratulations and welcome, Lu Xugang! (Can we call you by your full name as your signature, or do you have any preference on that? I use my first name here, some Asian people use their nicknames, etc.) Tomoko 2022年6月1日(水) 23:16 Nhat Nguyen : > > Congrats, Lu Xugang! > > On Wed, Jun 1, 2022

Re: Welcome Chris Hegarty as Lucene committer

Congratulations and welcome, Chris! Tomoko 2022年6月1日(水) 23:17 Nhat Nguyen : > Welcome, Chris! > > On Wed, Jun 1, 2022 at 8:49 AM Greg Miller wrote: > >> Welcome Chris! >> >> On Wed, Jun 1, 2022 at 2:04 PM Mayya Sharipova >> wrote: >> > >> > Welcome and congratulations, Chris! >> > >> > On

Re: [VOTE] Migration to GitHub issue from Jira (LUCENE-10557)

need to collect 15 "+1" from committers or just 15 votes (regardless of the > opinion)? > > Best > Patrick > > On Mon, May 30, 2022 at 8:41 AM Tomoko Uchida < > tomoko.uchida.1...@gmail.com> wrote: > >> Hi everyone! >> >> As we had previous

[VOTE] Migration to GitHub issue from Jira (LUCENE-10557)

Hi everyone! As we had previous discussion thread [1], I propose migration to GitHub issue from Jira. It'd be technically possible (see [2] for details) and I think it'd be good for the project - not only for welcoming new developers who are not familiar with Jira, but also for improving the

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

But why set such an extra bar? My fear is that if such things are decided by the opinions of a few members, the result shouldn't yield a good result for the future. It isn't my goal to just pass the vote. [1] https://projects.apache.org/committee.html?lucene Tomoko Tomoko 2022年5月26日(木) 10:17 Tomoko Uchi

  1   2   3   4   5   6   7   8   >