It's not up to Lucene and Solr, as it is an Apache Infrastructure thing. It is
also unclear as to provenance w/ GIT. So, even for all of GITs benefits, it's
a non-starter at this point Foundation wise, so no need for a flamewar at all.
For the record, yes, I deal with dozens of patches at a
[
https://issues.apache.org/jira/browse/LUCENE-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reopened LUCENE-2367:
-
Lucene Fields: (was: [New])
CartesianPolyFilterBuilder has problems around the poles
Looks like we are ready to go to merge the Lucene and Solr dev mailing lists.
The new list will be d...@lucene.apache.org. All existing subscribers will
automatically be subscribed to the new list. For more info, see
https://issues.apache.org/jira/browse/INFRA-2567.
-Grant
+1
On Apr 14, 2010, at 5:22 PM, Michael McCandless wrote:
On Wed, Apr 14, 2010 at 12:06 AM, Marvin Humphrey
mar...@rectangular.com wrote:
Essentially, we're free to break back compat within Lucy at any time, but
we're not able to break back compat within a stable fork like Lucy1,
Lucy2,
I do think major versions should be able to read the previous version index.
Still, even being able to do that is no guarantee that it will produce correct
results. Likewise, even having an upgrade tool is no guarantee that correct
results will be produced. So, my take is that we strive for
...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
--
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem using Solr/Lucene:
http://www.lucidimagination.com/search
On Apr 15, 2010, at 4:21 PM, Shai Erera wrote:
+1 on the Analyzers as well.
Earwin, I think I don't mind if we introduce migrate() elsewhere rather than
on IW. What I meant to say is that if we stick w/ index format back-compat
and ongoing migration, then such a method would be useful on
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856857#action_12856857
]
Grant Ingersoll commented on LUCENE-2184:
-
Thanks, Nicolas. Applied
On Apr 14, 2010, at 12:49 AM, Robert Muir wrote:
On Wed, Apr 14, 2010 at 12:06 AM, Marvin Humphrey mar...@rectangular.com
wrote:
New class names would work, too.
I only mention that for the sake of completeness, though -- it's not a
suggestion.
Right, to me this is just as bad.
In
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856902#action_12856902
]
Grant Ingersoll commented on LUCENE-2359:
-
Nicolas,
Why the change in the best
LUCENE-2359 changed the best fit calculation. I admit, I'm not entirely
certain which one is right, so I thought we should step back and talk about
what we are trying to achieve.
Please correct me if/where I am wrong.
Looking at the problem of tiers/tiles/grids in general, we are taking a
On Apr 14, 2010, at 11:06 AM, Chris Male wrote:
Hi,
My understanding of the benefits of the new algorithm is that it means a
lower tier level resulting in fewer boxes, but more documents inside those
boxes that are outside of the search radius.
While having fewer boxes means fewer
Lucene Eurocon 2010
18-21 May 2010 | Prague
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
--
Grant Ingersoll
http
On Apr 14, 2010, at 12:12 PM, Chris Male wrote:
Hi,
On Wed, Apr 14, 2010 at 6:07 PM, Grant Ingersoll gsing...@apache.org wrote:
On Apr 14, 2010, at 11:06 AM, Chris Male wrote:
Hi,
My understanding of the benefits of the new algorithm is that it means a
lower tier level
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856963#action_12856963
]
Grant Ingersoll commented on LUCENE-2359:
-
Thanks, Nicolas. To me, based
directions/axis
Best regards,
Nicolas
2010/4/14 Chris Male gento...@gmail.com
Hi,
On Wed, Apr 14, 2010 at 6:07 PM, Grant Ingersoll gsing...@apache.org wrote:
On Apr 14, 2010, at 11:06 AM, Chris Male wrote:
Hi,
My understanding of the benefits of the new algorithm
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12857054#action_12857054
]
Grant Ingersoll commented on LUCENE-2359:
-
So, you're saying then that your
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12857158#action_12857158
]
Grant Ingersoll commented on LUCENE-2359:
-
Reverted the last patch and the other
[
https://issues.apache.org/jira/browse/LUCENE-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned LUCENE-2367:
---
Assignee: Grant Ingersoll
CartesianPolyFilterBuilder has problems around the poles
[
https://issues.apache.org/jira/browse/LUCENE-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-2367.
-
Resolution: Fixed
Committed Nicolas' patch to trunk
CartesianPolyFilterBuilder has
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856565#action_12856565
]
Grant Ingersoll commented on LUCENE-2359:
-
Committed Nicolas' updates to trunk
[
https://issues.apache.org/jira/browse/LUCENE-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-2366.
-
Resolution: Fixed
Committed revision 933754.
LLRect.createBox returned box does
On Apr 13, 2010, at 2:09 PM, Shai Erera wrote:
And I guess that what bothers me the most is that it feels to me like we're
trying to protect people from stuff we haven't yet received complaints on (at
least none that I'm aware of),
I think we have, they just aren't explicitly stated b/c
FYI, this is for real. Some have asked me if it is made up. I don't know who
owns that user, so we should ask on infra, I suspect. Also, this applies to
all user accounts too on JIRA.
On Apr 13, 2010, at 12:25 PM, r...@apache.org wrote:
Dear Lucene Developers,
You are receiving this
-Original Message-
From: Grant Ingersoll [mailto:gsi...@gmail.com] On Behalf Of Grant
Ingersoll
Sent: Wednesday, April 14, 2010 1:50 AM
To: java-dev@lucene.apache.org
Subject: Re: issues.apache.org compromised: please update your
passwords
FYI, this is for real. Some have asked me
+1
On Apr 9, 2010, at 9:59 PM, John Wang wrote:
Hi:
I am using the SmartChineseAnalyzer class and it is great!
Was wondering if we should have a set of chinese stopwords. The default
set containts only punctuations.
Thanks
-John
Reporter: Grant Ingersoll
Priority: Minor
Test Lat/Lon: 89.9, 50 and 89.9, -130.0. Try a point near those two points,
like 89.8,50 and a distance of 200.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853121#action_12853121
]
Grant Ingersoll commented on LUCENE-2359:
-
Nicolas,
How does this compare to what
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853156#action_12853156
]
Grant Ingersoll commented on LUCENE-2359:
-
bq. handles East AND West tiles when
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853164#action_12853164
]
Grant Ingersoll commented on LUCENE-2359:
-
AFAICT, that is covered by the current
On Apr 2, 2010, at 2:50 AM, Babak Farhang wrote:
[Late to this party, but thought I'd chime in]
I think this layer concept is right on. But I'm wondering about the
life cycle of these layers. Do layers live forever? Or do they
collapse at some point? (Like, as I think was already pointed
I'm pleased to announce that the Lucene PMC has voted to add Uwe Schindler to
the PMC. Uwe has been doing a lot of work in Lucene and Solr, including
several of the last releases in Lucene.
Please join me in extending congratulations to Uwe!
-Grant Ingersoll
PMC Chair
(working together to rework the whole thing).
I put up a patch on https://issues.apache.org/jira/browse/LUCENE-2359. How
does your's compare? Can you post it?
Commit of this work should be done by Chris very soon.
Hope it will help.
Nicolas
2010/3/31 Grant Ingersoll gsing...@apache.org
On Apr 1, 2010, at 8:22 AM, Helleringer, Nicolas wrote:
I did put a comment on the jira issue pointing to the code I wrote inside
Chris Male perspective.
He answered on the JIRA topic as well.
Yep, saw that. If you wish for that code to be in Lucene, you need to post it
as a patch to
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-2359.
-
Resolution: Fixed
Committed revision 929956.
CartesianPolyFilterBuilder doesn't
On Apr 1, 2010, at 9:09 AM, Helleringer, Nicolas wrote:
2010/4/1 Grant Ingersoll gsing...@apache.org
No.
The longitude has an effect because of the projection used to go from a
spherical world to a flat coordinates system.
See http://www.nsshutdown.com/projects/lucene/whitepaper
On Apr 1, 2010, at 1:22 PM, Helleringer, Nicolas wrote:
I did. It is bugged.
https://issues.apache.org/jira/browse/LUCENE-1921 It has come up before.
It has also been re worked and will be patched (this weekend If I can) and
comitted by Chris afterwards.
slight reword: can be committed
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-2184.
-
Resolution: Fixed
Fix Version/s: 3.1
CartesianPolyFilterBuilder doesn't
[
https://issues.apache.org/jira/browse/LUCENE-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12852045#action_12852045
]
Grant Ingersoll commented on LUCENE-2350:
-
Once this is in, let's apply a global
Anyone know what the point of this code is from the CartesianPolyFilterBuilder:
code
shape = getShapeLoop(shape, ctp, latX, longX, latY, longY);
if (longX2 != 0.0) {
if (longX2 != 0.0) {
if (longX == 0.0) {
longX = longX2;
longY = 0.0;
shape =
Issue Type: Bug
Components: contrib/spatial
Affects Versions: 3.0.1, 3.0, 2.9.2, 2.9.1, 2.9
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
Priority: Minor
Test case:
Points all around the globe, plus two points at 0, 179.9 and 0
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2359:
Attachment: LUCENE-2359.patch
Fix. Will commit today or tomorrow. Going to double check
.
Cheers,
Mark
From: Grant Ingersoll gsing...@apache.org
To: java-dev@lucene.apache.org
Sent: Mon, 29 March, 2010 13:11:56
Subject: Re: Incremental Field Updates
On Mar 29, 2010, at 2:26 AM, Mark Harwood wrote:
Of course introducing the idea of updates also introduces
On Mar 29, 2010, at 2:26 AM, Mark Harwood wrote:
Of course introducing the idea of updates also introduces the notion of a
primary key and there's probably an entirely separate discussion to be had
around user-supplied vs Lucene-generated keys.
Not sure I see that need. Can you
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851013#action_12851013
]
Grant Ingersoll commented on LUCENE-2184:
-
Note, this bug exists for the min case
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned LUCENE-2184:
---
Assignee: Grant Ingersoll
CartesianPolyFilterBuilder doesn't properly account
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2184:
Attachment: LUCENE-2184.patch
Here's a patch. All tests still pass
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851043#action_12851043
]
Grant Ingersoll commented on LUCENE-2184:
-
Committed revision 928860 w/ the patch
, Grant Ingersoll wrote:
First off, this is something I've had in my head for a long time, but don't
have any code.
As many of you know, one of the main things that vexes any search engine
based on an inverted index is how to do fast updates of just one field w/o
having to delete and re-add
[
https://issues.apache.org/jira/browse/LUCENE-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850505#action_12850505
]
Grant Ingersoll commented on LUCENE-1879:
-
Thanks, Shai, I had indeed misread
First off, this is something I've had in my head for a long time, but don't
have any code.
As many of you know, one of the main things that vexes any search engine based
on an inverted index is how to do fast updates of just one field w/o having to
delete and re-add the whole document like we
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850072#action_12850072
]
Grant Ingersoll commented on LUCENE-2215:
-
bq. Let's be careful about
So, should we start thinking about a Modules dir at the same level as
Lucene/Solr where shared, non-core code lives?
For starters, I think spatial and analyzers could go there.
Proposal:
lucene/
solr/
modules/
analyzers
spatial
others (highlighter, faceting, ...)
I guess in some
Refactor/Cleanup Lucene Spatial
---
Key: LUCENE-2350
URL: https://issues.apache.org/jira/browse/LUCENE-2350
Project: Lucene - Java
Issue Type: Improvement
Reporter: Grant Ingersoll
Lucene spatial
Welcome!
On Mar 26, 2010, at 11:04 AM, Shai Erera wrote:
Thanks!
I'm very excited to join such a great and talented team. Following the
tradition, here's my short bio:
I'm 31 years old, married with 3 kids (although these 1+2 3 !). I
hold a M.Sc. in computer science from the University
[
https://issues.apache.org/jira/browse/LUCENE-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850322#action_12850322
]
Grant Ingersoll commented on LUCENE-1879:
-
First off, I haven't looked at the code
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849843#action_12849843
]
Grant Ingersoll commented on LUCENE-2215:
-
Mike, don't you think, though
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849961#action_12849961
]
Grant Ingersoll commented on LUCENE-2215:
-
Yeah, but one could make the argument
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849193#action_12849193
]
Grant Ingersoll commented on LUCENE-2215:
-
{quote}
I must admit I don't like
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
Priority: Minor
As the title says.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849207#action_12849207
]
Grant Ingersoll commented on LUCENE-2215:
-
I'm saying PagingColl. doesn't even
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849216#action_12849216
]
Grant Ingersoll commented on LUCENE-2215:
-
{quote}
The only complication I see
I see that Test has TEST_CURRENT_VERSION for version, but what about Benchmark?
Seems we should be using the latest and greatest, but LUCENE_CURRENT is
deprecated.
-Grant
-
To unsubscribe, e-mail:
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2343:
Attachment: LUCENE-2343.patch
Add support for benchmarking collectors
Add support
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849295#action_12849295
]
Grant Ingersoll commented on LUCENE-2343:
-
I intend to commit today or tomorrow
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849390#action_12849390
]
Grant Ingersoll commented on LUCENE-2343:
-
bq. can be written as
Class.forName
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849397#action_12849397
]
Grant Ingersoll commented on LUCENE-2343:
-
bq. In the patch you write
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849405#action_12849405
]
Grant Ingersoll commented on LUCENE-2343:
-
bq. I wasn't talking about the name
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2343:
Attachment: LUCENE-2343.patch
I think this addresses all of Shai's concerns.
Add
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-2343.
-
Resolution: Fixed
Fix Version/s: 3.1
Committed revision 927178.
Add support
[
https://issues.apache.org/jira/browse/LUCENE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849536#action_12849536
]
Grant Ingersoll commented on LUCENE-2343:
-
Should be in the contrib/benchmark
https://issues.apache.org/jira/browse/INFRA-2567
On Mar 22, 2010, at 11:44 AM, Grant Ingersoll wrote:
Shall we merge the dev mailing lists? This should reduce the cross-posting
and can be completely automated (other than you may have to update your
client-side filters) and was part
On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently a lusolr test-trunk is done as a branch inside solr
(https://svn.apache.org/repos/asf/lucene/solr/branches/newtrunk). The
question is, where
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
--
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem using Solr/Lucene:
http://www.lucidimagination.com/search
Quick Status on where we are at:
The new trunk for the merge is now open:
https://svn.apache.org/repos/asf/lucene/dev/trunk/ All committers should have
the same rights that they had before.
Please do all development on those.
The new mailing list has been requested:
On Mar 23, 2010, at 10:09 AM, Grant Ingersoll wrote:
3. Other nightly build stuff. My cron tabs, etc. I will update them to
point at the new trunk.
OK, I updated my cron tab for the site check out of Lucene. Not sure who
handles Solr
I'm still slightly confused on in order and out of order collectors. I
mean, I get what they do, but, if I'm implementing a new collector (see
https://issues.apache.org/jira/browse/LUCENE-2215) that is going to be part of
core, should I implement two versions: one for in order and one for out
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848795#action_12848795
]
Grant Ingersoll commented on LUCENE-2127:
-
Hey Jason,
My tests are inconclusive
On Mar 23, 2010, at 1:20 PM, Michael McCandless wrote:
You can implement just the out of order collector, since it subsumes
the in-order case, and all will work fine.
However, if the collector can save CPU when docs are known to arrive
in-order (not all collectors can) it'd be good to make
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848842#action_12848842
]
Grant Ingersoll commented on LUCENE-2215:
-
I think in order to properly implement
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2215:
Attachment: LUCENE-2215.patch
Here's an update of Aaron's work with the following changes
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848904#action_12848904
]
Grant Ingersoll commented on LUCENE-2215:
-
bq. BTW, I've noticed that you don't
Shall we merge the dev mailing lists? This should reduce the cross-posting and
can be completely automated (other than you may have to update your client-side
filters) and was part of the plan to merge dev efforts.
I'd propose it be called lucene-solr-...@l.a.o. I can put in an issue for
On Mar 22, 2010, at 12:43 PM, Ryan McKinley wrote:
Logistically, how would this work?
would d...@lucene.apache.org be an alias for java-dev and solr-dev? or
a whole new list?
I thought of d...@l.a.o, but we still have other dev lists under the PMC, so
didn't want to imply it was the only
On Mar 19, 2010, at 12:04 PM, Chris Male wrote:
Hi Alex,
Its a direction that is still under heavy development but its definitely the
direction I would like it go.
I think once the code merge happens, I can easily bring in the updates I made
too. For instance, I've added a fair number
On Mar 16, 2010, at 3:51 AM, Michael Busch wrote:
On 3/16/10 12:43 AM, Simon Willnauer wrote:Me too. I don't have the time to
follow IRC in addition to jira and mailinglists. I know I've been missing
stuff, because in the past I commented on jira issues and later was told that
my
On Mar 16, 2010, at 10:18 AM, Mark Miller wrote:
On 03/16/2010 10:09 AM, Yonik Seeley wrote:
On Tue, Mar 16, 2010 at 2:51 AM, Michael Buschbusch...@gmail.com wrote:
Also, we're in review-and-commit process, not commit-and-review. Changes
have to be
proposed, discussed and ideally
On Mar 16, 2010, at 2:47 PM, Steven A Rowe wrote:
On 03/16/2010 at 6:06 AM, Michael McCandless wrote:
Does anyone know how other projects fold in IRC...?
I gather from the deafening silence that we'll have to figure it out as we
go...
I think some (not all) of the discomfort associated
On Mar 16, 2010, at 3:24 PM, Mark Miller wrote:
On 03/16/2010 02:57 PM, Grant Ingersoll wrote:
On Mar 16, 2010, at 2:47 PM, Steven A Rowe wrote:
On 03/16/2010 at 6:06 AM, Michael McCandless wrote:
Does anyone know how other projects fold in IRC...?
I gather from
On Mar 14, 2010, at 8:25 PM, Yonik Seeley wrote:
On Sun, Mar 14, 2010 at 5:47 PM, Mark Miller markrmil...@gmail.com wrote:
On 03/14/2010 06:37 PM, Grant Ingersoll wrote:
On Mar 14, 2010, at 2:03 PM, Uwe Schindler wrote:
This time a +1 without discuss :-)
Yeah, but Uwe
On Mar 14, 2010, at 6:47 PM, Mark Miller wrote:
On 03/14/2010 06:37 PM, Grant Ingersoll wrote:
On Mar 14, 2010, at 2:03 PM, Uwe Schindler wrote:
This time a +1 without discuss :-)
Yeah, but Uwe, the thread was DISCUSS, not VOTE! :-)
I had a whole spiel about earning
On Mar 15, 2010, at 1:25 PM, Mark Miller wrote:
On 03/15/2010 08:33 AM, Grant Ingersoll wrote:
Right, Mark. I think we would be effectively raising the bar to some extent
for what it takes to be a committer.
That's part of my point though - some are contrib committers with a lower bar
Per the vote on general@ to merge committers, I've given Lucene and Solr
committers access to the two trunks.
-Grant
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
Given the notion of one project, one set of committers, I think we should do
away with the notion of contrib committers for java-dev and just have everyone
be committers. Practically speaking, this would make all existing contrib
committers be core committers. I think the notion of contrib
: Grant Ingersoll [mailto:gsi...@gmail.com] On Behalf Of Grant
Ingersoll
Sent: Sunday, March 14, 2010 5:54 PM
To: java-dev@lucene.apache.org
Subject: [DISCUSS] Do away with Contrib Committers and make core
committers
Given the notion of one project, one set of committers, I think we
should do
Congrats!
Tradition has it, Chris, that you provide a brief intro on yourself upon
becoming a new committer, so let's hear it!
-Grant
On Mar 12, 2010, at 9:17 AM, Mark Miller wrote:
I am happy to announce the Lucene PMC has accepted Chris Male as a
contrib committer!
Chris has been
On Mar 12, 2010, at 10:00 AM, Chris Male wrote:
Although I live in Amsterdam, I am actually from New Zealand so it feels good
to finally have kiwi representation.
+1. I've always wanted to go there! I'll have to pick your brain on it next
time I'm in Amsterdam over a pint.
-Grant
On Mar 10, 2010, at 1:52 PM, Mark Miller wrote:
On 03/10/2010 01:48 PM, Robert Muir wrote:
On Wed, Mar 10, 2010 at 1:40 PM, Shai Ereraser...@gmail.com wrote:
I wrote that I defaulted to Whitespace for convenience reasons only. Now you
don't need to specify anything if you don't care how
On Mar 1, 2010, at 2:51 AM, Michael McCandless wrote:
Yeah in the case of DirectoryReader/MultiReader, I'd like for them to
be final, not for performance but for door-shutting (ie the same
reason we make analyzers final).
Door shutting often is not a good thing, especially in a project like
To me, this is stuff that can go on the wiki or somewhere else, otherwise over
time, there will be others to add in, etc. We could simply add a pointer to
the wiki page in the README.
On Feb 24, 2010, at 11:55 PM, Shai Erera wrote:
Hi
I always find it annoying when I checkout the code to
1 - 100 of 1597 matches
Mail list logo
