Hi Michael The Apache way of for any user to provide changes is to first discuss them on the mailing list then submit a JIRA issue to track the work.
Regards, -- George > -----Original Message----- > From: Michael Garski [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 25, 2008 1:25 PM > To: lucene-net-user@incubator.apache.org > Subject: Lucenenet-106 > > Just a quick note on the issue described in LUCENENET-106. > Yes, the field cache and the filters will leak memory over > time due to how the cache is implemented. In Java it is done > with a weak hashmap so that when the searcher is gc'd, the > data that is cached is gc'd as well. I believe Digy posted a > patch for filters using a dual-collection approach using > .NET's weak references and a similar approach could be > implemented for the field cache. > > There are a few other changes that are specific to .NET that > could be made as well, such as using fields marked with > ThreadStatic as opposed to ThreadLocalStorage. What is the > best way for users to make such changes? My first thought is > that if you have a change, to open a JIRA issue and attach a > patch so that it can be reviewed by the community and if > found to be appropriate, then committed by a committer. Any > feedback on this? > > Michael > > -----Original Message----- > From: George Aroush [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 25, 2008 9:51 AM > To: lucene-net-user@incubator.apache.org > Subject: RE: Apache Lucene.Net.2.3.1 build 001 "Alpha" is now > available > > Hi DIGY, > > A 2.1 release would be a good exercise at working on a > release process to meet the Apache release requirement. The > process is time consuming and requires review and approval by > PMC. I have done it once in the past with 1.9. > > The two issues you highlighted, specially 106, I like to know > why this is an issue with 2.1 but not with 2.0 or prior. I > know we had this issue with earlier releases, but it was > addressed without such a significant change of introducing a > new class. > > In the next few days, I will review existing open JIRA issues > and comment accordingly. > > Regards, > > -- George > > >
