+1 (binding)
On Tue, May 12, 2020 at 9:18 PM Koji Sekiguchi
wrote:
> +1
>
> Koji
>
> On 2020/05/12 16:36, Dawid Weiss wrote:
> > Dear Lucene and Solr developers!
> >
> > According to an earlier [DISCUSS] thread on the dev list [2], I am
> > calling for a vote on the proposal to make Solr a top-l
+1
Koji
On 2020/05/12 16:36, Dawid Weiss wrote:
Dear Lucene and Solr developers!
According to an earlier [DISCUSS] thread on the dev list [2], I am
calling for a vote on the proposal to make Solr a top-level Apache
project (TLP) and separate Lucene and Solr development into two
independent ent
I agree this is a procedural vote. Here's my +1 for the proposal.
Shai
On Tue, May 12, 2020, 23:07 Simon Willnauer
wrote:
> I agree this is not a code change category vote. It’s a majority vote. -1s
> are not vetos.
>
> Simon
>
> On 12. May 2020, at 21:17, Atri Sharma wrote:
>
>
> I would ar
Alan and I worked out how to do this on the PR, and the change was made
without affecting the API signatures.
I am now working on cutting the bugfix release, it doesn't look like there
are any more pending issues to backport. Please follow the usual
conventions if you need to backport to this bran
I agree this is not a code change category vote. It’s a majority vote. -1s are
not vetos.
Simon
> On 12. May 2020, at 21:17, Atri Sharma wrote:
>
>
> I would argue against that — this is more of a project level decision with no
> changes to the core code base per se — more of restructuring
Dawid,
Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
I wanted to clarify that only PMC members cast binding votes and not
committers.
Also,
I am about to re-read the rules here but I think this is a procedural vote.
Also, considering almost all procedural changes would impact the code in
some way, I don't think anything would pass if we were to put stuff in the
"code modification" category as getting a single veto would stop all
progr
It's hard to make a decision because it seems to have pros and cons.
Basically, I agree to separate but there are some questions.
So I don't not vote right now.
1) Release version
Currently, versions of Lucene and Solr are aligned, how will they be
managed in the future?
Other people took Elastics
This is a procedural vote. Code is not affected. The future of each
project diverges from the same git commit.
Dawid
On Tue, May 12, 2020 at 9:08 PM Ishan Chattopadhyaya
wrote:
>
> This is in the code modification category, since code will be modified as
> result of this proposal.
>
> On Wed, 1
I would argue against that — this is more of a project level decision with
no changes to the core code base per se — more of restructuring of it. Sort
of how a sub project becomes a TLP.
On Wed, 13 May 2020 at 00:38, Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> This is in the code m
This is in the code modification category, since code will be modified as
result of this proposal.
On Wed, 13 May, 2020, 12:27 am Shawn Heisey, wrote:
> On 5/12/2020 1:36 AM, Dawid Weiss wrote:
> > According to an earlier [DISCUSS] thread on the dev list [2], I am
> > calling for a vote on the p
On 5/12/2020 1:36 AM, Dawid Weiss wrote:
According to an earlier [DISCUSS] thread on the dev list [2], I am
calling for a vote on the proposal to make Solr a top-level Apache
project (TLP) and separate Lucene and Solr development into two
independent entities.
+1 (pmc)
We should clarify exactl
-1 (committer)
On Tue, May 12, 2020 at 1:14 PM Chris Hostetter
wrote:
>
> : Therefore, the proposal is to separate Solr from under Lucene TLP, and
> : make it a TLP on its own. The initial structure of the new PMC,
> : committer base, git repositories and other managerial aspects can be
> : work
: Therefore, the proposal is to separate Solr from under Lucene TLP, and
: make it a TLP on its own. The initial structure of the new PMC,
: committer base, git repositories and other managerial aspects can be
: worked out during the process if the decision passes.
:
: Please indicate one of the
-1 (binding)
On Tue, May 12, 2020 at 12:37 AM Dawid Weiss wrote:
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development
+1
On Tue, May 12, 2020 at 11:20 AM Ryan Ernst wrote:
>
> +1 (binding)
>
> On Tue, May 12, 2020 at 12:37 AM Dawid Weiss wrote:
>>
>> Dear Lucene and Solr developers!
>>
>> According to an earlier [DISCUSS] thread on the dev list [2], I am
>> calling for a vote on the proposal to make Solr a top-
Would appreciate any contribution, Ilan.
Please look at https://issues.apache.org/jira/browse/SOLR-12823 and contribute
there (create a JIRA user if necessary).
Jan
> 12. mai 2020 kl. 17:06 skrev Ilan Ginzburg :
>
> I could work on a PR to remove it in Solr 9, unless you think it's
> super tri
+1 (binding)
On Tue, May 12, 2020 at 12:37 AM Dawid Weiss wrote:
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development
+1
> On May 12, 2020, at 3:36 AM, Dawid Weiss wrote:
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if
I could work on a PR to remove it in Solr 9, unless you think it's
super tricky work.
Ilan
On Tue, May 12, 2020 at 3:32 PM Erick Erickson wrote:
>
> Definitely +1, but I won’t have the bandwidth to help.
>
> > On May 12, 2020, at 9:03 AM, Jan Høydahl (Jira) wrote:
> >
> >
> >[
> > https://
+1 (binding)
Andi..
> On May 12, 2020, at 00:37, Dawid Weiss wrote:
>
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr d
+1 (binding)
On Tue, May 12, 2020 at 7:21 PM Ignacio Vera wrote:
> +1 (binding)
>
> On Tue, May 12, 2020 at 3:38 PM Tomás Fernández Löbbe <
> tomasflo...@gmail.com> wrote:
>
>> -1 (binding)
>>
>>
+1 (binding)
On Tue, May 12, 2020 at 3:38 PM Tomás Fernández Löbbe
wrote:
> -1 (binding)
>
>
-1 (binding)
Definitely +1, but I won’t have the bandwidth to help.
> On May 12, 2020, at 9:03 AM, Jan Høydahl (Jira) wrote:
>
>
>[
> https://issues.apache.org/jira/browse/SOLR-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105402#comment-17105402
> ]
>
I'll give a perspective that comes more from the user's / "market" point
of view as at OSC we onboard lots of new organizations into Solr.
- Most new users incorrectly think of Solr as an independent Apache
project, and many will have little knowledge or awareness of Lucene itself
until given the
+1 (binding)
~ David
+1 (binding)
On Tue, May 12, 2020 at 8:41 AM Steve Rowe wrote:
> +1
>
> --
> Steve
>
> > On May 12, 2020, at 3:36 AM, Dawid Weiss wrote:
> >
> > Dear Lucene and Solr developers!
> >
> > According to an earlier [DISCUSS] thread on the dev list [2], I am
> > calling for a vote on the proposal to
+1
--
Steve
> On May 12, 2020, at 3:36 AM, Dawid Weiss wrote:
>
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr developmen
+1, this is long overdue.
It will indeed be quite a bit of work to separate everything, but I think
the long term benefits to both projects will be massive, making that
one-time cost very much worth it.
Thanks for raising this Dawid!
Mike McCandless
http://blog.mikemccandless.com
On Tue, May
+1
On Tue, May 12, 2020 at 3:37 AM Dawid Weiss wrote:
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
>
+1 (binding)
Le mar. 12 mai 2020 à 14:00, Simon Willnauer a
écrit :
> +1 binding
>
> Sent from a mobile device
>
> > On 12. May 2020, at 13:33, Jason Gerlowski
> wrote:
> >
> > -1 (binding)
> >
> >> On Tue, May 12, 2020 at 7:31 AM Alan Woodward
> wrote:
> >>
> >> +1 (binding)
> >>
> >> Alan W
+1 binding
Sent from a mobile device
> On 12. May 2020, at 13:33, Jason Gerlowski wrote:
>
> -1 (binding)
>
>> On Tue, May 12, 2020 at 7:31 AM Alan Woodward wrote:
>>
>> +1 (binding)
>>
>> Alan Woodward
>>
On 12 May 2020, at 12:06, Jan Høydahl wrote:
>>>
>>> +1 (binding)
>>>
>>>
-1 (binding)
On Tue, May 12, 2020 at 7:31 AM Alan Woodward wrote:
>
> +1 (binding)
>
> Alan Woodward
>
> > On 12 May 2020, at 12:06, Jan Høydahl wrote:
> >
> > +1 (binding)
> >
> > Jan Høydahl
> >
> >> 12. mai 2020 kl. 09:36 skrev Dawid Weiss :
> >>
> >> Dear Lucene and Solr developers!
> >>
> >
+1 (binding)
Alan Woodward
> On 12 May 2020, at 12:06, Jan Høydahl wrote:
>
> +1 (binding)
>
> Jan Høydahl
>
>> 12. mai 2020 kl. 09:36 skrev Dawid Weiss :
>>
>> Dear Lucene and Solr developers!
>>
>> According to an earlier [DISCUSS] thread on the dev list [2], I am
>> calling for a vote on
One advantage I find with the way Elasticsearch and Lucene interact is that ES
doesn’t depend on the master branch. We upgrade our master branch frequently
to keep up to date with the latest release branch, and that lets us find
regressions or API problems pretty quickly, but it also insulates
+1 (binding)
Jan Høydahl
> 12. mai 2020 kl. 09:36 skrev Dawid Weiss :
>
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr dev
Hi,
here is also my +1
I have a few objections about the process, but in general it's a good idea.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Dawid Weiss
> Sent: Tuesday, May 12, 2020 9:37 AM
> To:
Oh, here is my +1 (binding).
Dawid
On Tue, May 12, 2020 at 9:36 AM Dawid Weiss wrote:
>
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Luce
Thanks for suggesting this and bringing this forward to a vote, Dawid.
I'm in favor of the proposal; +1 (binding)
Best,
Christian
On Tue, May 12, 2020 at 4:37 PM Dawid Weiss wrote:
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> call
+1 from me (binding)
Karl
On Tue, May 12, 2020 at 3:54 AM Atri Sharma wrote:
> +1 (binding).
>
> Regards,
>
> Atri
>
> On Tue, 12 May 2020 at 13:07, Dawid Weiss wrote:
>
>> Dear Lucene and Solr developers!
>>
>> According to an earlier [DISCUSS] thread on the dev list [2], I am
>> calling for a
+1 (binding).
Regards,
Atri
On Tue, 12 May 2020 at 13:07, Dawid Weiss wrote:
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and So
Dear Lucene and Solr developers!
According to an earlier [DISCUSS] thread on the dev list [2], I am
calling for a vote on the proposal to make Solr a top-level Apache
project (TLP) and separate Lucene and Solr development into two
independent entities.
To quickly recap the reasons and consequence
43 matches
Mail list logo
