Thanks Dawid. That JIRA was a private/protected one, that's why. I'll email you
the contents in private :)
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 17. sep. 2019 kl. 07:52 skrev Dawid Weiss :
>
> Hi Jan,
>
> Funny, I don't have permission to see or comment o
Hi Jan,
Funny, I don't have permission to see or comment on:
https://issues.apache.org/jira/browse/SOLR-13648
Anybody knows why this is the case?
Yes, simple-xml is a dependency of Carrot2 (clustering contrib's
default implementation). I'm working on having it removed on next
iteration of Carrot
+1 to all that Gus said. On a fresh project then indeed perhaps we would
use GitHub issues but it's not nearly so compelling at this point with so
much rich history in JIRA, not to mention those issues being referenced in
commit messages.
Is the point to lower barriers for contributors that are n
FWIW, One thing that needs to be figured out is how github would
accommodate security issues (or how the process for those issues would
change). Does github have the ability to assign roles and visibility
(could be I haven't really worked with organizations on GitHub, all my
clients have been on j
This is no reproduce output yet, in my mind that is waiting with the tests
seed work that I started on but needs review and finishing.
tests_jvms is jvms and no user param naming is yet thought out or final
when it comes to modifying the build. I've instead stuck to exposing few
things and expecti
Is there any reason at all that we need to hold on to JIRA? ASF allows us to
move all issue handling over to GH, I'd like us to consider such a move.
Until then, I made a script that "diffs" GH and JIRA and outputs a report, see
https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts
Jason,
Here we go https://issues.apache.org/jira/browse/SOLR-13764
On Mon, Sep 16, 2019 at 3:05 PM Jason Gerlowski
wrote:
> Hi Mikhail,
>
> I'm having trouble understanding the exact syntax you're proposing.
> Is there a jira where the syntax is described in a little more detail?
> If not, wou
Some misc questions after playing around with gradle on this branch for a
bit today in no particular order...
: tests_jvms=5
...
: test_jvms is controlled by us and defaults to the number of cores detected
: / 2.
If tests_jvms is a lucene/solr specific property, that needs to
be in a
> On 16 Sep 2019, at 19:38, Yonik Seeley wrote:
>
> > - PR is opened - should automatically create a jira if it doesn’t exist yet
>
> What were the reasons behind this? Shouldn't a JIRA just be optional if we
> started with a PR?
That’s why we need to discuss this :)
I remember that at some
Maybe making a backup first would improve things?
My first feeling was just let the user do this, but I work in a bunch of
envs and it's very nice to have.
At worst the task description and any doc can say WARNING!: we are going to
edit your file if you do this, there will be a .bak or something.
That's against Gradle best practices, if you look it up, this is the way
Gradle is intended to work. Settings like
That task description can warn about editing your file, but I feel it's
pretty safe given that you have to decide to use it.
We don't remove anything and we don't change controversia
> - PR is opened - should automatically create a jira if it doesn’t exist
yet
What were the reasons behind this? Shouldn't a JIRA just be optional if we
started with a PR?
-Yonik
Agree, would be much better if the issue title came first. When reading mails
on my phone I have to open each mail to see which issue it is about since the
email client will only display N first chars of the mail title :(
Jan Høydahl
> 16. sep. 2019 kl. 17:42 skrev Erick Erickson :
>
> Hmmm, I
> On 16 Sep 2019, at 17:55, Ishan Chattopadhyaya
> wrote:
>
>> Committers attending (at least some part of) the meeting, in no particular
>> order: Erik Hatcher, Anshum Gupta, David Smiley, Gus Heck, Noble Paul, Varun
>> Thacker, Ishan Chattopadhyaya, Tomás Löbbe, and yours truly.
>
> Also
+1 to start working on 8.3
Did you mean "start a vote" when you wrote "release the artifacts"? It
got me wondering because I don't think we frequently managed to go
from cutting a branch to releasing artifacts in so little time in the
past.
On Mon, Sep 16, 2019 at 5:52 PM Ishan Chattopadhyaya
wr
I’m going to suspend these until we build up a better backlog of tests since a
number of machines weren’t being collected by Hoss’ rollups. I’ll continue to
gather the rollups every week, but for a while I don’t think it’s worth
cluttering your inbox.
Sounds good to me except I think we need to make ref guide part of
releases. We are now able to commit docs along with code and an issue
should not be resolved and features not merged unless docs are in and ready
for release.
On Mon, Sep 16, 2019, 11:52 AM Ishan Chattopadhyaya <
ichattopadhy...@gm
> Committers attending (at least some part of) the meeting, in no particular
> order: Erik Hatcher, Anshum Gupta, David Smiley, Gus Heck, Noble Paul, Varun
> Thacker, Ishan Chattopadhyaya, Tomás Löbbe, and yours truly.
Also, Tim Allison, Joel Bernstein, Jason Gerlowski. (Did we miss out
someone
https://bugs.openjdk.java.net/browse/JDK-8189192 makes it appear that
Direct I/O is (or may be?) available now in JDK's since JDK10. Should
we try using that API in NativeUnixDirectory in order to avoid JNI
calls?
-
To unsubscribe
Hi all,
We have a lot of unreleased features and fixes. I propose that we cut
a 8.3 branch in two weeks (in order to have sufficient time to bake in
all in-progress features). If there are no objections to doing so, I
can volunteer for the release as an RM and plan for cutting a release
branch on 3
Hmmm, I’ve noticed one thing that would be nice. Currently I’m using OS X mail
client. It tries to thread conversations
Ideally, anything with the title containing:
SOLR-13734 JWTAuthPlugin to support multiple issuers”
would be grouped together. But since the title is prepended with:
"[GitHub]
Hi Mikhail,
I'm having trouble understanding the exact syntax you're proposing.
Is there a jira where the syntax is described in a little more detail?
If not, would you care to put together a writeup on a jira somewhere?
It's hard (for me at least) to weigh in as things are currently.
Best,
Ja
Hey folks,
Some of the committers attended the Activate 2019 conference, which took place
in Washington, DC on Sep 10-13.
The schedule was packed, so we managed to only have a ~1hr meeting during a
lunch break - nonetheless, I think it was still very productive!
Committers attending (at least
23 matches
Mail list logo
