Re: Lucene 9.3.0 release

Thanks Adrien, it is indeed a big change, also would be nice to see benchmarks after it is merged. So, Ignacio, please don't wait for LUCENE-10592, we will not be able to make it for tomorrow. On Tue, Jul 19, 2022 at 10:38 AM Adrien Grand wrote: > While I can understand the excitement about

Re: Lucene 9.3.0 release

While I can understand the excitement about LUCENE-10592, it's also a big change, maybe we should not even try to get it in before cutting the branch? On Tue, Jul 19, 2022 at 4:09 PM Mayya Sharipova wrote: > Thanks for the reminder about the release, Ignacio! > About LUCENE-10592

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

> 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 notification on issues@ before the script is started - maybe, issue watchers will notice that if there are comments from someone. Other opinions?

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 Uchida : > >

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

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 wrote: > > 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

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

> > > 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 > completed. > > Is this going to send 10k emails to the mailing list? I’ll need to update my filters so that these skip my

Re: Lucene 9.3.0 release

Thanks for the reminder about the release, Ignacio! About LUCENE-10592 I will see what progress we can make today, and will let you know before Wednesday at 9:00 CEST. On Tue, Jul 19, 2022 at 7:12 AM Michael Sokolov wrote: > Thanks for

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

> 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 repo next week. Could some people help/test it (randomly open/close issues, add

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

On Tue, Jul 19, 2022 at 8:48 AM Tomoko Uchida wrote: > > 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 > completed. > Is this going to send 10k emails to the mailing list? I’ll

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

> 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 completed. > 2. Send a message to dev@ stating new issues should now be opened in github > 3. Start the migration In theory, it would

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

> Yes, it won't be a really atomic switch While it may not be completely atomic, could it be closer? GitHub already supports new issues, developers are just advised against opening there. Could the order of events be: 1. Make Jira read only 2. Send a message to dev@ stating new issues should now

Re: Lucene 9.3.0 release

Thanks for checking, but please don't wait for LUCENE-10577. It's not clear when that might get resolved On Mon, Jul 18, 2022, 10:42 AM Ignacio Vera wrote: > Just a quick reminder I plan to cut the 9.3 branch this Wednesday at 9:00 > CEST. Let me know if there is any issue. > > @Mike: I see

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