[
https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745251#action_12745251
]
Michael Busch commented on LUCENE-1823:
---
I think Solr has a feature similar to what
On 8/19/09 3:16 PM, Uwe Schindler wrote:
0 issues! Congrats everyone. 2.9 was quite a beast.
So looks like we should get a few things in order.
1. Anyone dying to be release manager? I think I could do it, but I'm
kind of pressed for time ...
2. Lets start crawling all over this release - bugs
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745236#action_12745236
]
Adriano Crestani commented on LUCENE-1768:
--
{quote}
we should rename RangeQue
Uwe Schindler wrote:
>> 0 issues! Congrats everyone. 2.9 was quite a beast.
>>
>> So looks like we should get a few things in order.
>>
>> 1. Anyone dying to be release manager? I think I could do it, but I'm
>> kind of pressed for time ...
>>
>> 2. Lets start crawling all over this release - bugs/
> 0 issues! Congrats everyone. 2.9 was quite a beast.
>
> So looks like we should get a few things in order.
>
> 1. Anyone dying to be release manager? I think I could do it, but I'm
> kind of pressed for time ...
>
> 2. Lets start crawling all over this release - bugs/javadoc/packaging etc.
>
I hadn't settled on me being the RM yet ;) Though if no one else steps
up, I will be.
I was suggesting a kind of earlier, looser test jar than what we have
previously done as an RC (essentially a nightly (which are hard to find
lately IME - last one I got I had to dig through Hudson) of trunk)
When I was the RM I usually sent out a note in advance with a tentative
schedule, i.e. code freeze date, length of code freeze period, release
date (again, all tentative of course). Then the community could give
feedback on that proposed schedule and could plan accordingly.
Michael
On 8/19/0
On 8/19/09 11:43 AM, Grant Ingersoll wrote:
On Aug 19, 2009, at 2:13 PM, Yonik Seeley wrote:
On Wed, Aug 19, 2009 at 1:52 PM, Grant Ingersoll
wrote:
the RM should follow the release procedure as specified.
Wiki documents are normally not official - anyone can modify them, and
people have be
Not sure - though if not now, than extremely imminently. I have no
problem giving a bit of time for people to weigh in on that.
I'm trying to get a feel for what the community wants to do before
actually putting
anything up or sending anything out to java-user. I'm prepped to go when
it makes
So, are we under a code freeze now? And only doing doc/breakers?
-Grant
On Aug 19, 2009, at 3:08 PM, Mark Miller wrote:
Okay, I can do the test/beta release dist and host on
people.apache.org.
Anyone have any pref on what we call this? Its not really a release
candidate per say, though I
Okay, I can do the test/beta release dist and host on people.apache.org.
Anyone have any pref on what we call this? Its not really a release
candidate per say, though I have no
problem calling it that. We can go from rc1 to rc20 for all it matters.
--
- Mark
http://www.lucidimagination.com
On Aug 19, 2009, at 2:13 PM, Yonik Seeley wrote:
On Wed, Aug 19, 2009 at 1:52 PM, Grant
Ingersoll wrote:
the RM should follow the release procedure as specified.
Wiki documents are normally not official - anyone can modify them, and
people have been with little/no discussion. I'll admit th
On Wed, Aug 19, 2009 at 1:52 PM, Grant Ingersoll wrote:
> the RM should follow the release procedure as specified.
Wiki documents are normally not official - anyone can modify them, and
people have been with little/no discussion. I'll admit that I can't
always follow java-dev, so I may have misse
On Aug 19, 2009, at 11:17 AM, Yonik Seeley wrote:
A final note - AFAIK, the ReleaseTodo
http://wiki.apache.org/jakarta-lucene/ReleaseTodo is for the purpose
of helping people do releases - it's not an official release process
where every step must be followed... these are only guidelines.
There'
[
https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745146#action_12745146
]
Mark Miller commented on LUCENE-1823:
-
Option to not die on bad syntax - keep what wor
[
https://issues.apache.org/jira/browse/LUCENE-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1225:
--
Priority: Minor (was: Critical)
Lucene Fields: [Patch Available] (was: [Patch Availa
On Wed, Aug 19, 2009 at 10:49 AM, Mark Miller wrote:
> 3. In regards to that - I'd like to suggest that we don't do the release
> branch early for 2.9. I know we normally make the release
> branch so that further dev can continue on trunk. In this case I don't
> think that is wise. I propose that
0 issues! Congrats everyone. 2.9 was quite a beast.
So looks like we should get a few things in order.
1. Anyone dying to be release manager? I think I could do it, but I'm
kind of pressed for time ...
2. Lets start crawling all over this release - bugs/javadoc/packaging etc.
3. In regards t
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Smith updated LUCENE-1821:
--
Description:
Now that searching is done on a per segment basis, there is no way for a Scorer
to know
[
https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745048#action_12745048
]
Alex Vigdor commented on LUCENE-1824:
-
The failing test was due to an extra whitespace
[
https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Vigdor updated LUCENE-1824:
Attachment: LUCENE-1824.patch
> FastVectorHighlighter truncates words at beginning and end of frag
[
https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Vigdor updated LUCENE-1824:
Attachment: (was: LUCENE-1824-test.patch)
> FastVectorHighlighter truncates words at beginning
[
https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Vigdor updated LUCENE-1824:
Attachment: (was: LUCENE-1824.patch)
> FastVectorHighlighter truncates words at beginning and
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745045#action_12745045
]
Tim Smith commented on LUCENE-1821:
---
"rely on" it is
> Weight.scorer() not passed doc o
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745044#action_12745044
]
Mark Miller commented on LUCENE-1821:
-
Looks great!
I still almost want to say rely o
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Smith updated LUCENE-1821:
--
Attachment: LUCENE-1821.patch
Here's a patch that adds getIndexReaderBase(IndexReader reader) to Index
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745041#action_12745041
]
Tim Smith commented on LUCENE-1821:
---
One more pass
{code}
13. LUCENE-1483: When searchi
[
https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Vigdor updated LUCENE-1824:
Attachment: LUCENE-1824-test.patch
> FastVectorHighlighter truncates words at beginning and end of
[
https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Vigdor updated LUCENE-1824:
Attachment: (was: LUCENE-1824-test.patch)
> FastVectorHighlighter truncates words at beginning
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745039#action_12745039
]
Mark Miller commented on LUCENE-1821:
-
I think thats a good idea. I think that last se
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745036#action_12745036
]
Tim Smith commented on LUCENE-1821:
---
Concerning the changelog, i feel the below should b
[
https://issues.apache.org/jira/browse/LUCENE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-1813.
-
Resolution: Fixed
Committed revision 805769.
Thanks Andrzej and also everyone who provided feed
[
https://issues.apache.org/jira/browse/LUCENE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-1794.
-
Resolution: Fixed
Committed revision 805766.
> implement reusableTokenStream for all contrib an
[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744970#action_12744970
]
Michael McCandless commented on LUCENE-1821:
BTW contrib/spatial has exactly
34 matches
Mail list logo
