[jira] Commented: (SOLR-777) backword match search, for domain search etc.

[ https://issues.apache.org/jira/browse/SOLR-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633160#action_12633160 ] Koji Sekiguchi commented on SOLR-777: - bq. Koji, I'd stick it in contrib. Oops. I didn't

Solr 1.3.0 Release Lessons Learned

Hey Solr Devs, So, 1.3.0 is out. Whew! I think I survived. I hope y'all did too. At any rate, I promised Lars I would follow up on his comment: http://lucene.markmail.org/message/ynsnkigymbv7kfqn?q=%5BVOTE%5D+Solr+1%2E3 , so here goes. So, what are the lessons learned? What can we do

Re: Solr 1.3.0 Release Lessons Learned

I'd suggest we shoot for every 6 mos. or so, and maybe even some bug fix releases more often. Maybe we should even do something where we have a stable and an experimental release. Especially for big things like the distributed search stuff this will potentially attract more people to test

Re: Solr 1.3.0 Release Lessons Learned

where we have a stable and an experimental release. Good idea. Also may be good to nominate a release manager. It seemed like features were being thrown in constantly that were perhaps beyond the intended scope (was there one?) of SOLR 1.3. Probably next time, maybe 2-3 large features and

Re: Solr 1.3.0 Release Lessons Learned

On Sep 22, 2008, at 11:37 AM, Jason Rutherglen wrote: where we have a stable and an experimental release. Good idea. Also may be good to nominate a release manager. It seemed like features were being thrown in constantly that were perhaps beyond the intended scope (was there one?) of SOLR

[jira] Created: (SOLR-784) Support loading queries from external files in QuerySenderListener

Support loading queries from external files in QuerySenderListener -- Key: SOLR-784 URL: https://issues.apache.org/jira/browse/SOLR-784 Project: Solr Issue Type: Improvement

Re: Solr 1.3.0 Release Lessons Learned

On Mon, Sep 22, 2008 at 7:04 PM, Grant Ingersoll [EMAIL PROTECTED]wrote: Hey Solr Devs, So, 1.3.0 is out. Whew! I think I survived. I hope y'all did too. At any rate, I promised Lars I would follow up on his comment:

Re: Solr 1.3.0 Release Lessons Learned

On 22-Sep-08, at 10:34 AM, Shalin Shekhar Mangar wrote: I'd like to propose a more pro-active approach to release planning by the community. At any given time, let's have two versions in JIRA. Only those issues which a committer has assigned to himself should be in the first un-released

Re: Solr 1.3.0 Release Lessons Learned

I agree with Mike. The simpler you make it the higher the chances of the plan being followed. I had to re-read the part about un-released versions. Moreover, rigid rules work great when people doing the work can really spend quality time on the project. This means that people working on

[jira] Commented: (SOLR-765) ant example fails if example/work directory doesn't exist

[ https://issues.apache.org/jira/browse/SOLR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633436#action_12633436 ] Hoss Man commented on SOLR-765: --- 1) my previous comment was in regards to your possible to

Re: Solr 1.3.0 Release Lessons Learned

I guess I went a bit overboard with the plan :-) Yes, I agree about the point on hard deadlines. However, I do feel that marking an issue to the next immediate release should represent a priority to the issue from us. The core of my suggestion is continuous release planning to ensure releasing

[jira] Updated: (SOLR-765) ant example fails if example/work directory doesn't exist

[ https://issues.apache.org/jira/browse/SOLR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-765: --- Attachment: SOLR-765.patch Right, fair enough. I'm attaching a new patch which calls mkdir on

[jira] Created: (SOLR-785) Distributed SpellCheckComponent

Distributed SpellCheckComponent --- Key: SOLR-785 URL: https://issues.apache.org/jira/browse/SOLR-785 Project: Solr Issue Type: Improvement Components: spellchecker Reporter: Shalin Shekhar

Re: Solr 1.3.0 Release Lessons Learned

Yes, I think more consistent use of Fix for version will already be a very good step forward. We started using that more consistently only right before the release, I'd say. That is one easy thing we can do and it will allow us to quickly tell us where we are, whether we have enough meat for

Re: facet.sort parameter

: The redesign I propose is changing the facet.sort parameter from a boolean to a : string and explicitely specify the sort method (with a default method if the : parameter isn't specified). You'd use facet.sort=count to sort by facet count : and something like facet.sort=lex to sort