Re: [important] call for 1.3 planning
On Jun 5, 2008, at 7:45 PM, Mike Klaas wrote: On 21-May-08, at 4:45 PM, Mike Klaas wrote: There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. The list of JIRA issues currently labeled 1.3 can be found here: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12310230fixfor=12312486 Let's try to get an assignee for every issue in that list by a week from now. If nobody steps up for an issue in that time, I'll assume it is low enough priority to move post-1.3. This would also be a good time to add any issues that you want to champion for 1.3. That brings us down to 20 issues, with only 2 unassigned: SOLR-424 and SOLR-410. I removed a few of the feature issues with no assignee. Seems like the big things that need to get done are: - componented spellchecking I think we are pretty close on this one.
Re: [important] call for 1.3 planning
On 21-May-08, at 4:45 PM, Mike Klaas wrote: There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. The list of JIRA issues currently labeled 1.3 can be found here: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12310230fixfor=12312486 Let's try to get an assignee for every issue in that list by a week from now. If nobody steps up for an issue in that time, I'll assume it is low enough priority to move post-1.3. This would also be a good time to add any issues that you want to champion for 1.3. That brings us down to 20 issues, with only 2 unassigned: SOLR-424 and SOLR-410. I removed a few of the feature issues with no assignee. Seems like the big things that need to get done are: - componented spellchecking - contrib area + data import handler - distributed search -Mike
Re: [important] call for 1.3 planning
On May 22, 2008, at 5:59 PM, Otis Gospodnetic wrote: I agree. Lots of what Jason is doing looks good, but like I pointed the other day, needs a lot more explanation, at least for dense people like moi. My guess is, if we want to be aggressive with 1.3, that none of Jason's stuff will make it because the changes are too radical, unless somebody very comfortable with Solr guts sits down, reviews everything, and can commit with confidence. I agree also -- the goals of ocean search look great, and I'm very happy there is an effort to integrate whatever is possible. But I don't have the time or energy to wade through this right now. For the larger goal of integrating features like Realtime facets and tagging, it is probably best to get a solid 1.3 release out as soon as possible. Once the release is out, there is a little more wiggle room to to make some of these changes with the confidence there is time before the next release. ryan
Re: [important] call for 1.3 planning
I don't know exactly what Hoss has in mind, but for one thing it would
mean we would need to support this in the future.
In general, changes like this get discussed for a while -- flushing
out any potential implications -- before they get added. The process
can be a bit annoying (and slow) but overall helps make sure things
stay solid.
As I said earlier, I think the best thing would be a quick release of
1.3 limited (mostly) to cleaning up loose ends -- then a broader game
plan on how to integrate oceansearch in 1.4/2.0
On May 22, 2008, at 5:41 PM, Jason Rutherglen wrote:
Please explain the maintenence considerations.
On Thu, May 22, 2008 at 5:35 PM, Chris Hostetter [EMAIL PROTECTED]
wrote:
: SOLR-567 is simple enough to add to the list.
I can't speak for anyone else, but SOLR-567 certianly doesn't meet my
definition of simple ... this one line, by itself, opens up a lot
of
potential maintenence considerations and requires some serious API
review/discussion...
-public final class SolrCore {
+public class SolrCore {
-Hoss
Re: [important] call for 1.3 planning
SOLR-560. ;-) SOLR-502. On May 21, 2008, at 7:45 PM, Mike Klaas wrote: There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. The list of JIRA issues currently labeled 1.3 can be found here: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12310230fixfor=12312486 Let's try to get an assignee for every issue in that list by a week from now. If nobody steps up for an issue in that time, I'll assume it is low enough priority to move post-1.3. This would also be a good time to add any issues that you want to champion for 1.3. (This isn't meant to be a final list, just something to help get us started. Most of the unassigned issues were reported by committers, so that should hopefully make it easy to figure out the assignee.) -Mike
Re: [important] call for 1.3 planning
: SOLR-567 is simple enough to add to the list.
I can't speak for anyone else, but SOLR-567 certianly doesn't meet my
definition of simple ... this one line, by itself, opens up a lot of
potential maintenence considerations and requires some serious API
review/discussion...
-public final class SolrCore {
+public class SolrCore {
-Hoss
Re: [important] call for 1.3 planning
Please explain the maintenence considerations.
On Thu, May 22, 2008 at 5:35 PM, Chris Hostetter [EMAIL PROTECTED]
wrote:
: SOLR-567 is simple enough to add to the list.
I can't speak for anyone else, but SOLR-567 certianly doesn't meet my
definition of simple ... this one line, by itself, opens up a lot of
potential maintenence considerations and requires some serious API
review/discussion...
-public final class SolrCore {
+public class SolrCore {
-Hoss
Re: [important] call for 1.3 planning
I agree. Lots of what Jason is doing looks good, but like I pointed the other
day, needs a lot more explanation, at least for dense people like moi. My
guess is, if we want to be aggressive with 1.3, that none of Jason's stuff will
make it because the changes are too radical, unless somebody very comfortable
with Solr guts sits down, reviews everything, and can commit with confidence.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Chris Hostetter [EMAIL PROTECTED]
To: solr-dev@lucene.apache.org
Sent: Thursday, May 22, 2008 5:35:47 PM
Subject: Re: [important] call for 1.3 planning
: SOLR-567 is simple enough to add to the list.
I can't speak for anyone else, but SOLR-567 certianly doesn't meet my
definition of simple ... this one line, by itself, opens up a lot of
potential maintenence considerations and requires some serious API
review/discussion...
-public final class SolrCore {
+public class SolrCore {
-Hoss
Re: [important] call for 1.3 planning
On Wed, May 21, 2008 at 7:45 PM, Mike Klaas [EMAIL PROTECTED] wrote: There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. +1 (I've been away from my email for a few days... just now trying to catch up). -Yonik The list of JIRA issues currently labeled 1.3 can be found here: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12310230fixfor=12312486 Let's try to get an assignee for every issue in that list by a week from now. If nobody steps up for an issue in that time, I'll assume it is low enough priority to move post-1.3. This would also be a good time to add any issues that you want to champion for 1.3. (This isn't meant to be a final list, just something to help get us started. Most of the unassigned issues were reported by committers, so that should hopefully make it easy to figure out the assignee.) -Mike
[important] call for 1.3 planning
There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. The list of JIRA issues currently labeled 1.3 can be found here: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12310230fixfor=12312486 Let's try to get an assignee for every issue in that list by a week from now. If nobody steps up for an issue in that time, I'll assume it is low enough priority to move post-1.3. This would also be a good time to add any issues that you want to champion for 1.3. (This isn't meant to be a final list, just something to help get us started. Most of the unassigned issues were reported by committers, so that should hopefully make it easy to figure out the assignee.) -Mike
Re: [important] call for 1.3 planning
SOLR-567 is simple enough to add to the list. On Wed, May 21, 2008 at 7:45 PM, Mike Klaas [EMAIL PROTECTED] wrote: There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. The list of JIRA issues currently labeled 1.3 can be found here: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12310230fixfor=12312486 Let's try to get an assignee for every issue in that list by a week from now. If nobody steps up for an issue in that time, I'll assume it is low enough priority to move post-1.3. This would also be a good time to add any issues that you want to champion for 1.3. (This isn't meant to be a final list, just something to help get us started. Most of the unassigned issues were reported by committers, so that should hopefully make it easy to figure out the assignee.) -Mike
