Once the code/patch in the issue is put/committed to SVN, it means it will be in the next release. You get your patch committed faster if it's clear, well written and explained, if it comes with a unit test if it's a code change, and so on.
Otis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simpy -- http://www.simpy.com/ - Tag - Search - Share ----- Original Message ---- From: Michael Kimsal <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Friday, April 27, 2007 1:47:06 PM Subject: Re: case sensitivity What's the procedure then for something to get included in the next release? Thanks again all! On 4/27/07, Michael Kimsal <[EMAIL PROTECTED]> wrote: > > So I just create my own 'issue' first? OK. Thanks. > > On 4/27/07, Ryan McKinley <[EMAIL PROTECTED]> wrote: > > > > Michael Kimsal wrote: > > > Can you point me to the process for submitting these small > > patches? I'm > > > looking at the jira site but don't see much of anything there > > outlining a > > > process for submitting patches. Sorry to be so basic about this, but > > I'm > > > trying to follow correct procedures on both sides of the aisle, so to > > > speak. > > > > > > > Check: http://wiki.apache.org/solr/HowToContribute > > > > Essentially you will create a new issue on JIRA, then upload a svn diff > > to that issue. > > > > holler if you have any troubles > > > > ryan > > > > > > > -- > Michael Kimsal > http://webdevradio.com > -- Michael Kimsal http://webdevradio.com
