Re: Tracking contributors uniquely

2024-02-13 Thread Ishan Chattopadhyaya
Looking up CHANGES.txt is inevitable. Sometimes reporting a bug in JIRA is also a valid contribution. That gets tracked in CHANGES.txt. On Tue, 13 Feb 2024 at 12:41, David Smiley wrote: > I'm working on a script to track contributors so that (A) we can track > project health for ASF board report

Re: Nightly Solr Ref Guide; search is out-of-date

2024-02-13 Thread Jan Høydahl
Have you done a force refresh in your browser? The search index is client side. Jan Høydahl > 12. feb. 2024 kl. 23:45 skrev David Smiley : > > I went looking for the latest/nightly ref guide because I wanted to > check out how something recently added but not yet released looks in > the documen

unsubscribe

2024-02-13 Thread Bauchwitz, Leonardo

AW: unsubscribe

2024-02-13 Thread Bauchwitz, Leonardo
Von: Bauchwitz, Leonardo Gesendet: Dienstag, 13. Februar 2024 05:52 An: dev@solr.apache.org Betreff: [Possibly spoofed] unsubscribe - To unsubscribe, e-mail: dev-unsubscr...@solr.apache.o

Re: getIdField removed in Solr 9 but deprecation message in Solr 8 has no alternative specified

2024-02-13 Thread PJ Fanning
The legacy code that we have has tests that sets the router field and that uses the legacy getIdField method to retrieve this later. So hardcoding "id" is not enough for my use case. I have what seems like a working solution though. I get the router field from the doc collection. This code wor

PR milestones (was: PR labeling)

2024-02-13 Thread Christine Poerschke (BLOOMBERG/ LONDON)
Hello, So with more labeling in use now, I wondered if "Milestones" could also be useful e.g. correlated to releases like with (say) Lucene https://github.com/apache/lucene/milestones There would be implications for the release wizard/process presumably (closing milestones, creating new milest

Re: Tracking contributors uniquely

2024-02-13 Thread Chris Hostetter
: Looking up CHANGES.txt is inevitable. Sometimes reporting a bug in JIRA is : also a valid contribution. That gets tracked in CHANGES.txt. Agreed. Commit != Contribute. If it was that simple there wouldn't be any CHANGES.txt entries with more then one name. -Hoss http://www.lucidworks.co

Re: Tracking contributors uniquely

2024-02-13 Thread Ilan Ginzburg
Keep in mind the regulations in some part of the world if you plan to maintain a file containing "full name, primary email, and email aliases" For example https://europa.eu/youreurope/citizens/consumers/internet-telecoms/data-protection-online-privacy/index_en.htm Ilan On Tue, Feb 13, 2024 at 8:1

Re: [DISCUSS] Community Virtual Meetup, February 2024

2024-02-13 Thread Bruno Roustant
I vote for 2/23 Thanks Jason

Re: Tracking contributors uniquely

2024-02-13 Thread Jan Høydahl
We should encourage committers to include Author and Co-Authored-By tags in commit message even for patches in Jira. This way contributors are credited in git log history too. And it gives us a way to get rid of CHANGES.txt some beautiful day ☀️ Jan Høydahl > 13. feb. 2024 kl. 09:21 skrev Isha

Re: [DISCUSS] Community Virtual Meetup, February 2024

2024-02-13 Thread Ilan Ginzburg
Thanks for organizing this. I vote *not* 2/20 and *not* 2/22. On Tue 13 Feb 2024 at 22:53, Bruno Roustant wrote: > I vote for 2/23 > > Thanks Jason >