Re: [Lucene.Net] Re: Signing Binary Releases
That makes sense. We've been serving up the distributions from ~/lucene.net/site/download in our svn repo through the website. I guess with this release, once it passes the IPMC vote, we can create a lucene.net under http://www.apache.org/dist/incubator/ and serve from there? Should we also move our past release artifacts there? Thanks, Troy On Tue, Feb 22, 2011 at 9:08 PM, Stefan Bodewig bode...@apache.org wrote: On 2011-02-22, Troy Howard wrote: I found that we have an extant KEYS.TXT at: https://svn.apache.org/repos/asf/incubator/lucene.net/site/download/KEYS.txt Would it be acceptable to simply add to that file, or is this file in the wrong location? The location doesn't really matter but you should copy it to wherever the distribution files will live as well. Stefan
RE: [Lucene.Net] Lucene.Net Tasks due by 2/28
I'm out of town this weekend, but I'm hoping to get one or two designs (likely just screenshots) attached to the JIRA so people can give me some feedback. I'll make it quick turn around and won't leave it open for feedback long though. If anyone has ideas / thoughts, samples they like, comment on the JIRA for the website stuff. I spoke with Troy this evening and it's likely after we get the logo contest completed we'd redesign to fit the logo better - so I'm not too worried about what this first iteration looks like. Also, I am not a designer ;) ~P From: thowar...@gmail.com Date: Wed, 23 Feb 2011 00:32:03 -0800 To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] Lucene.Net Tasks due by 2/28 All, I've recently been updating JIRA a lot and that's causing a lot of noise on the dev list. Also, because of that noise, I fear that some of the more important details of those changes might be passing by unnoticed. Mostly, I'm trying to get the project cleaned up by the end of the month. The goal is that March will represent a month of building out our new infrastructure and creating our first new release as a team (2.9.4). To that end, I'd like to resolve some of the outstanding questions about tooling so we can get started building out solutions with those tools. Also, I'd like to see our new status and efforts announced publicly, but I'm hesitant to draw much attention to the project until the website is updated. Additionally, I'd like to take a moment to apologize a bit for moving at such a rapid pace. I realize this is not sustainable and could cause some people to feel alienated if they don't have the time or energy right this second to match that pace. I also feel a bit self-conscious and am concerned that I'm being a little to much 'me', and perhaps not enough 'we'. I have been taking a lot of liberty regarding the project direction, bypassing some opportunities for community discussion and voting, in the interests of pushing the project forward and catching up a bit of lost time. Once we get past this initial push, I hope that we can slow down a bit, and maintain a healthy forward-moving pace with plenty of time allotted for discussion, group decision making and voting. The Apache Way is the way this project will succeed and thrive, and that requires all of us. So, that said, the outstanding tasks, which we can hopefully complete by next Monday are: Troy Howard: LUCENENET-381 - Official release of Lucene.Net 2.9.2 Sergey Mirvoda: LUCENENET-398 - LUCENENET-391 Prepare the code for ingestion Michael Herndon: LUCENENET-400 - Evaluate tooling for continuous integration server Prescott Nasser: LUCENENET-379 - Clean up Lucene.Net website LUCENENET-379 / LUCENENET-403 - Improve site layout and design LUCENENET-379 / LUCENENET-402 - Update website to reflect current status and information LUCENENET-379 / LUCENENET-401 - Update website to be Apache CMS based Alex Thompson: LUCENENET-380 - Evaluate Sharpen as a port tool Does anyone feel less than confident about being able to complete those tasks on that schedule? Need any help? Want to change assignments? Anyone in the community want to get involved as a contributor on any of these tasks (or any of the open tasks in JIRA that are not listed here)? Sergey could probably use some help on Luke.Net. Prescott has a lot of work cut out for him on the website. Perhaps we should get the ball rolling on 2.9.4 task assignments for everyone else? Thanks, Troy
[Lucene.Net] [jira] Commented: (LUCENENET-403) Improve site layout and design
[ https://issues.apache.org/jira/browse/LUCENENET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998248#comment-12998248 ] Prescott Nasser commented on LUCENENET-403: --- Some sites that we are considering using as a base: http://www.zeromq.org/ - might be too simple for our needs, but like the cleanlyness https://bitbucket.org/ - dash of color, banner gives ample room for a call to action. http://flask.pocoo.org/ - another rather clean layout http://www.openoffice.org/ - I'm not a huge fan, but the call's to action are in your face, incorporating something like that is high on my list http://grafico.kilianvalkhof.com/ - really clean, probably too gray, not really an area to provide some navigation http://www.microsoft.com/visualstudio/en-us/ If you have thoughts, comments, etc post them here. I'm going to be working on this a lot in the next few days. Again, this will be temporary until we get the logo contest completed, and then we will likely redesign again. Improve site layout and design -- Key: LUCENENET-403 URL: https://issues.apache.org/jira/browse/LUCENENET-403 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Prescott Nasser Fix For: Lucene.Net 2.9.2 Improve the website layout and design. Current staging design is based off an extremely simplistic implementation of Apache CMS basic template using the default Apache CMS CSS styling. Let's try to make it look better and have a more intuitive navigational structure. See staging site at: http://lucene.net.staging.apache.org/lucene.net/ To edit content, please use: https://cms.apache.org/lucene.net/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Lucene.Net] Re: Signing Binary Releases
On 2011-02-23, Troy Howard wrote: That makes sense. We've been serving up the distributions from ~/lucene.net/site/download in our svn repo through the website. Ah, understood. This is not the way you should do it - in fact you should never have done. Releases are supposed to take advantage of the ASF mirror system and the mirrors pick up stuff from www.apache.org/dist The download page either only is a template for a CGI script provided by our infrastructure gurus or uses http://www.apache.org/dyn/closer.cgi/incubator/ (with an appropriate path replacing the /incubator/ part) to link to the things to download. It will never point to the mirrors for PGP signatures of MD5/SHA1 hashes, of course. I guess with this release, once it passes the IPMC vote, we can create a lucene.net under http://www.apache.org/dist/incubator/ and serve from there? I'd say you must. Should we also move our past release artifacts there? Old releases are supposed to be on http://archive.apache.org/dist/ which is a non-deleting mirror of http://www.apache.org/dist/. You could get all the old releases archived by putting them on www for a short time first but then all mirrors would pull them down just to delete them soon thereafter. We should ask infra whether there is a better way to move the old releases to the archive. Stefan
Re: [Lucene.Net] how to make the search not case sensitive
Thanks, I solved this problem. I found that if what i typed is lowercase, the result is not case senstive, e.g. if search for database it would return DATABASE, database. However, if what i typed is uppercase, the result is case sensitive, e.g. if search for DATABASE, no results would return. So I just transfer the input to lowercae using toLower(), and it works. Is there anyting wrong with this? Wen 2011/2/22 Peter Mateja peter.mat...@gmail.com Wen, You need to make sure that you are using the same analyzer when both indexing and searching in a particular index field. For instance, in your case, you need to ensure that the value DATABASE (in whatever field that is in) is indexed with the StandardAnalyzer. Then, use the StandardAnalyzer to search that field. This should find the match when you search for database, DATABASE, Database, etc, and return the original value stored as DATABASE. Of course, if you need case sensitivity, then you'd use the KeywordAnalyzer. If you've got a more complex index schema which requires different analyzers per field, then you'll need to look into using the PerFieldAnalyzerWrapper in order to correctly handle indexing and searching. Peter Mateja peter.mat...@gmail.com On Tue, Feb 22, 2011 at 3:13 PM, Wen Gao samuel.gao...@gmail.com wrote: Hi, I am using lucene's standard analyser to search, however, the search result is case sensitive. e.g, when i search for database, DATABASE could not return. I could store the typed items as lowercase, and store the stored data as lowercase as well, but in this case, the returned results would be lower case, instead of the original form. e.g, the returned results would be database instead of DATABASE. Any ideas? Wen
Re: [Lucene.Net] Phrase search with Wildcard query
Check that you're using the same analyzer that you indexed with to search against that particular field. Also, wildcard queries don't really handle spaces. I suggest using the query parser if you want to have multiple terms to search the same field by. Considering your previous query, you'll need to SetAllowLeadingWildcard(true) on the queryparser and remember that the default operator on the queryparser is OR. You may want to change that to AND considering your example. It's also not a good idea to start your wildcard query with a wildcard, as it can make searches extremely slow. You can use Luke (http://code.google.com/p/luke/) to write queries against your index, if you wanted to test your queries that way. It also uses the queryparser to parse it and gives you a human readable parsing of your query, you can see exactly how lucene interprets it. Christopher On Wed, Feb 23, 2011 at 7:51 AM, Wen Gao samuel.gao...@gmail.com wrote: Hi, I'm using Wildcard query to search phrases, but failed to get results. E.g. I search for *data man*,however, no result returned although there is a record of *data manage* in my index. I change the data man as *data*man* using following code: String s = * + s.Replace( , *) + *; WildcardQuery wildquery = new Lucene.Net.Search.WildcardQuery(new Lucene.Net.Index.Term(name, keyword)); ... searcher.Search(wildquery); It works if I only search part of phrase without 'space', e.g. the record returns when i type *data*. Any ideas? Thanks, Wen Gao
[Lucene.Net] JIRA issues for Java Lucene changes
Troy, I will start adding separate JIRA issues tonight. In the past do all the Java Lucene issues translate into .Net issues? Scott On Wed, Feb 23, 2011at 2:20 PM ,Troy Howard [mailto:thowar...@gmail.com] wrote: Scott, I would say the first task would be to collect all the Java changes up and create separate JIRA issues for each one. Thanks, Troy On Wed, Feb 23, 2011 at 9:16 AM, Lombard, Scott slomb...@kingindustries.com wrote: I am on vacation next week. So I won't be very helpful the next couple of days. I will be able take on some things for the 2.9.4 release. Are we going to break down the Java Lucene changes to individual items that need to be ported or is it going to be handled as one big task? Scott -Original Message- From: Troy Howard [mailto:thowar...@gmail.com] Sent: Wednesday, February 23, 2011 3:32 AM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] Lucene.Net Tasks due by 2/28 All, I've recently been updating JIRA a lot and that's causing a lot of noise on the dev list. Also, because of that noise, I fear that some of the more important details of those changes might be passing by unnoticed. Mostly, I'm trying to get the project cleaned up by the end of the month. The goal is that March will represent a month of building out our new infrastructure and creating our first new release as a team (2.9.4). To that end, I'd like to resolve some of the outstanding questions about tooling so we can get started building out solutions with those tools. Also, I'd like to see our new status and efforts announced publicly, but I'm hesitant to draw much attention to the project until the website is updated. Additionally, I'd like to take a moment to apologize a bit for moving at such a rapid pace. I realize this is not sustainable and could cause some people to feel alienated if they don't have the time or energy right this second to match that pace. I also feel a bit self-conscious and am concerned that I'm being a little to much 'me', and perhaps not enough 'we'. I have been taking a lot of liberty regarding the project direction, bypassing some opportunities for community discussion and voting, in the interests of pushing the project forward and catching up a bit of lost time. Once we get past this initial push, I hope that we can slow down a bit, and maintain a healthy forward-moving pace with plenty of time allotted for discussion, group decision making and voting. The Apache Way is the way this project will succeed and thrive, and that requires all of us. So, that said, the outstanding tasks, which we can hopefully complete by next Monday are: Troy Howard: LUCENENET-381 - Official release of Lucene.Net 2.9.2 Sergey Mirvoda: LUCENENET-398 - LUCENENET-391 Prepare the code for ingestion Michael Herndon: LUCENENET-400 - Evaluate tooling for continuous integration server Prescott Nasser: LUCENENET-379 - Clean up Lucene.Net website LUCENENET-379 / LUCENENET-403 - Improve site layout and design LUCENENET-379 / LUCENENET-402 - Update website to reflect current status and information LUCENENET-379 / LUCENENET-401 - Update website to be Apache CMS based Alex Thompson: LUCENENET-380 - Evaluate Sharpen as a port tool Does anyone feel less than confident about being able to complete those tasks on that schedule? Need any help? Want to change assignments? Anyone in the community want to get involved as a contributor on any of these tasks (or any of the open tasks in JIRA that are not listed here)? Sergey could probably use some help on Luke.Net. Prescott has a lot of work cut out for him on the website. Perhaps we should get the ball rolling on 2.9.4 task assignments for everyone else? Thanks, Troy This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you, King Industries, Inc. This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it
[Lucene.Net] [jira] Commented: (LUCENENET-399) Port changes from Java Lucene 2.9.3 and 2.9.4 releases
[
https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998559#comment-12998559
]
Digy commented on LUCENENET-399:
{quote}
Scott,
I would say the first task would be to collect all the Java changes up and
create separate JIRA issues for each one.
Thanks,
Troy
On Wed, Feb 23, 2011 at 9:16 AM, Lombard, Scott slombard@ wrote:
I am on vacation next week. So I won't be very helpful the next couple of
days. I will be able take on some things for the 2.9.4 release. Are we
going to break down the Java Lucene changes to individual items that need to
be ported or is it going to be handled as one big task?
Scott
{quote}
This is the location of of lucene 2.9.4
https://svn.apache.org/repos/asf/lucene/java/tags/lucene_2_9_4
It seems that we have to fix the modifications/additions and deletions between
revisions 912409 and 1040993.
There are 103 files (plus 34 pdf,xml,txt...files) affected and most of them
require just a few lines of change.
I don't think we need 70(#of issues of 2.9.3+2.9.4) or 103(# of affected files)
new issues just for this.
DIGY
{code}
src/test/org/apache/lucene/store/TestMultiMMap.javaAdded
src/test/org/apache/lucene/search/TestCachingSpanFilter.java Added
src/test/org/apache/lucene/index/TestSnapshotDeletionPolicy.java Added
src/test/org/apache/lucene/index/TestIsCurrent.javaAdded
src/test/org/apache/lucene/index/TestRollback.java Added
src/test/org/apache/lucene/index/TestIndexCommit.java Added
contrib/queryparser/src/test/org/apache/lucene/queryParser/core/nodes/TestQueryNode.java
Added
src/test/org/apache/lucene/index/TestNewestSegment.javaAdded
src/java/org/apache/lucene/analysis/standard/StandardTokenizer.javaModified
src/java/org/apache/lucene/analysis/standard/StandardTokenizerImpl.java
Modified
src/java/org/apache/lucene/analysis/PerFieldAnalyzerWrapper.java Modified
src/java/org/apache/lucene/analysis/tokenattributes/TermAttributeImpl.java
Modified
src/java/org/apache/lucene/analysis/Tokenizer.java Modified
src/java/org/apache/lucene/analysis/Token.java Modified
src/java/org/apache/lucene/search/FieldCache.java Modified
src/java/org/apache/lucene/search/CachingSpanFilter.java Modified
src/java/org/apache/lucene/search/TimeLimitingCollector.java Modified
src/java/org/apache/lucene/search/CachingWrapperFilter.javaModified
src/java/org/apache/lucene/search/WildcardTermEnum.javaModified
src/java/org/apache/lucene/search/FieldDoc.javaModified
src/java/org/apache/lucene/search/IndexSearcher.java Modified
src/java/org/apache/lucene/search/FieldCacheImpl.java Modified
src/java/org/apache/lucene/index/ByteBlockPool.javaModified
src/java/org/apache/lucene/index/FieldsReader.java Modified
src/java/org/apache/lucene/index/FieldsWriter.java Modified
src/java/org/apache/lucene/index/ParallelReader.java Modified
src/java/org/apache/lucene/index/SegmentReader.javaModified
src/java/org/apache/lucene/index/SnapshotDeletionPolicy.java Modified
src/java/org/apache/lucene/index/ReusableStringReader.java Modified
src/java/org/apache/lucene/index/MergePolicy.java Modified
src/java/org/apache/lucene/index/LogMergePolicy.java Modified
src/java/org/apache/lucene/index/StoredFieldsWriter.java Modified
src/java/org/apache/lucene/index/SegmentInfos.java Modified
src/java/org/apache/lucene/index/CheckIndex.java Modified
src/java/org/apache/lucene/index/ConcurrentMergeScheduler.java Modified
src/java/org/apache/lucene/index/MultiReader.java Modified
src/java/org/apache/lucene/index/IndexCommit.java Modified
src/java/org/apache/lucene/index/DirectoryReader.java Modified
src/java/org/apache/lucene/index/TermsHash.javaModified
src/java/org/apache/lucene/index/FilterIndexReader.javaModified
src/java/org/apache/lucene/index/SegmentMerger.javaModified
src/java/org/apache/lucene/index/TermsHashPerField.javaModified
src/java/org/apache/lucene/index/TermVectorsTermsWriter.java Modified
src/java/org/apache/lucene/index/DocumentsWriter.java Modified
src/java/org/apache/lucene/index/TermVectorsReader.javaModified
src/java/org/apache/lucene/index/TermVectorsTermsWriterPerField.java Modified
src/java/org/apache/lucene/index/IndexWriter.java Modified
src/java/org/apache/lucene/index/IndexFileDeleter.java Modified
src/java/org/apache/lucene/store/NIOFSDirectory.java Modified
src/java/org/apache/lucene/store/Directory.javaModified
src/java/org/apache/lucene/store/RAMOutputStream.java Modified
src/java/org/apache/lucene/store/MMapDirectory.javaModified
src/java/org/apache/lucene/store/RAMFile.java Modified
src/java/org/apache/lucene/store/NativeFSLockFactory.java Modified
[Lucene.Net] [jira] Updated: (LUCENENET-403) Improve site layout and design
[ https://issues.apache.org/jira/browse/LUCENENET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prescott Nasser updated LUCENENET-403: -- Attachment: layout1.zip Based mostly on bitbucket.org. Takes some elements from other stuff as well. Check out both index.html as the landing page, and then index2.html as potential internal pages. Improve site layout and design -- Key: LUCENENET-403 URL: https://issues.apache.org/jira/browse/LUCENENET-403 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Prescott Nasser Fix For: Lucene.Net 2.9.2 Attachments: layout1.zip Improve the website layout and design. Current staging design is based off an extremely simplistic implementation of Apache CMS basic template using the default Apache CMS CSS styling. Let's try to make it look better and have a more intuitive navigational structure. See staging site at: http://lucene.net.staging.apache.org/lucene.net/ To edit content, please use: https://cms.apache.org/lucene.net/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: [Lucene.Net] JIRA issues for Java Lucene changes
2.3.1-2.3.2 or 2.9.1 - 2.9.2 transitions were done with just a single patch, for ex. DIGY -Original Message- From: Lombard, Scott [mailto:slomb...@kingindustries.com] Sent: Wednesday, February 23, 2011 11:36 PM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] JIRA issues for Java Lucene changes Troy, I will start adding separate JIRA issues tonight. In the past do all the Java Lucene issues translate into .Net issues? Scott On Wed, Feb 23, 2011at 2:20 PM ,Troy Howard [mailto:thowar...@gmail.com] wrote: Scott, I would say the first task would be to collect all the Java changes up and create separate JIRA issues for each one. Thanks, Troy On Wed, Feb 23, 2011 at 9:16 AM, Lombard, Scott slomb...@kingindustries.com wrote: I am on vacation next week. So I won't be very helpful the next couple of days. I will be able take on some things for the 2.9.4 release. Are we going to break down the Java Lucene changes to individual items that need to be ported or is it going to be handled as one big task? Scott -Original Message- From: Troy Howard [mailto:thowar...@gmail.com] Sent: Wednesday, February 23, 2011 3:32 AM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] Lucene.Net Tasks due by 2/28 All, I've recently been updating JIRA a lot and that's causing a lot of noise on the dev list. Also, because of that noise, I fear that some of the more important details of those changes might be passing by unnoticed. Mostly, I'm trying to get the project cleaned up by the end of the month. The goal is that March will represent a month of building out our new infrastructure and creating our first new release as a team (2.9.4). To that end, I'd like to resolve some of the outstanding questions about tooling so we can get started building out solutions with those tools. Also, I'd like to see our new status and efforts announced publicly, but I'm hesitant to draw much attention to the project until the website is updated. Additionally, I'd like to take a moment to apologize a bit for moving at such a rapid pace. I realize this is not sustainable and could cause some people to feel alienated if they don't have the time or energy right this second to match that pace. I also feel a bit self-conscious and am concerned that I'm being a little to much 'me', and perhaps not enough 'we'. I have been taking a lot of liberty regarding the project direction, bypassing some opportunities for community discussion and voting, in the interests of pushing the project forward and catching up a bit of lost time. Once we get past this initial push, I hope that we can slow down a bit, and maintain a healthy forward-moving pace with plenty of time allotted for discussion, group decision making and voting. The Apache Way is the way this project will succeed and thrive, and that requires all of us. So, that said, the outstanding tasks, which we can hopefully complete by next Monday are: Troy Howard: LUCENENET-381 - Official release of Lucene.Net 2.9.2 Sergey Mirvoda: LUCENENET-398 - LUCENENET-391 Prepare the code for ingestion Michael Herndon: LUCENENET-400 - Evaluate tooling for continuous integration server Prescott Nasser: LUCENENET-379 - Clean up Lucene.Net website LUCENENET-379 / LUCENENET-403 - Improve site layout and design LUCENENET-379 / LUCENENET-402 - Update website to reflect current status and information LUCENENET-379 / LUCENENET-401 - Update website to be Apache CMS based Alex Thompson: LUCENENET-380 - Evaluate Sharpen as a port tool Does anyone feel less than confident about being able to complete those tasks on that schedule? Need any help? Want to change assignments? Anyone in the community want to get involved as a contributor on any of these tasks (or any of the open tasks in JIRA that are not listed here)? Sergey could probably use some help on Luke.Net. Prescott has a lot of work cut out for him on the website. Perhaps we should get the ball rolling on 2.9.4 task assignments for everyone else? Thanks, Troy This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you, King Industries, Inc. This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade
RE: [Lucene.Net] JIRA issues for Java Lucene changes
In the time needed to create 10s of issues, half of the fixes could be done :) DIGY -Original Message- From: Lombard, Scott [mailto:slomb...@kingindustries.com] Sent: Wednesday, February 23, 2011 11:36 PM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] JIRA issues for Java Lucene changes Troy, I will start adding separate JIRA issues tonight. In the past do all the Java Lucene issues translate into .Net issues? Scott On Wed, Feb 23, 2011at 2:20 PM ,Troy Howard [mailto:thowar...@gmail.com] wrote: Scott, I would say the first task would be to collect all the Java changes up and create separate JIRA issues for each one. Thanks, Troy On Wed, Feb 23, 2011 at 9:16 AM, Lombard, Scott slomb...@kingindustries.com wrote: I am on vacation next week. So I won't be very helpful the next couple of days. I will be able take on some things for the 2.9.4 release. Are we going to break down the Java Lucene changes to individual items that need to be ported or is it going to be handled as one big task? Scott -Original Message- From: Troy Howard [mailto:thowar...@gmail.com] Sent: Wednesday, February 23, 2011 3:32 AM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] Lucene.Net Tasks due by 2/28 All, I've recently been updating JIRA a lot and that's causing a lot of noise on the dev list. Also, because of that noise, I fear that some of the more important details of those changes might be passing by unnoticed. Mostly, I'm trying to get the project cleaned up by the end of the month. The goal is that March will represent a month of building out our new infrastructure and creating our first new release as a team (2.9.4). To that end, I'd like to resolve some of the outstanding questions about tooling so we can get started building out solutions with those tools. Also, I'd like to see our new status and efforts announced publicly, but I'm hesitant to draw much attention to the project until the website is updated. Additionally, I'd like to take a moment to apologize a bit for moving at such a rapid pace. I realize this is not sustainable and could cause some people to feel alienated if they don't have the time or energy right this second to match that pace. I also feel a bit self-conscious and am concerned that I'm being a little to much 'me', and perhaps not enough 'we'. I have been taking a lot of liberty regarding the project direction, bypassing some opportunities for community discussion and voting, in the interests of pushing the project forward and catching up a bit of lost time. Once we get past this initial push, I hope that we can slow down a bit, and maintain a healthy forward-moving pace with plenty of time allotted for discussion, group decision making and voting. The Apache Way is the way this project will succeed and thrive, and that requires all of us. So, that said, the outstanding tasks, which we can hopefully complete by next Monday are: Troy Howard: LUCENENET-381 - Official release of Lucene.Net 2.9.2 Sergey Mirvoda: LUCENENET-398 - LUCENENET-391 Prepare the code for ingestion Michael Herndon: LUCENENET-400 - Evaluate tooling for continuous integration server Prescott Nasser: LUCENENET-379 - Clean up Lucene.Net website LUCENENET-379 / LUCENENET-403 - Improve site layout and design LUCENENET-379 / LUCENENET-402 - Update website to reflect current status and information LUCENENET-379 / LUCENENET-401 - Update website to be Apache CMS based Alex Thompson: LUCENENET-380 - Evaluate Sharpen as a port tool Does anyone feel less than confident about being able to complete those tasks on that schedule? Need any help? Want to change assignments? Anyone in the community want to get involved as a contributor on any of these tasks (or any of the open tasks in JIRA that are not listed here)? Sergey could probably use some help on Luke.Net. Prescott has a lot of work cut out for him on the website. Perhaps we should get the ball rolling on 2.9.4 task assignments for everyone else? Thanks, Troy This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you, King Industries, Inc. This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret.
RE: [Lucene.Net] JIRA issues for Java Lucene changes
You're probably right DIGY. I will take a look at issues and create JIRA issues where the complexity deems it appropriate. I will comment or patch otherwise. Scott -Original Message- From: Digy [mailto:digyd...@gmail.com] Sent: Wednesday, February 23, 2011 5:02 PM To: lucene-net-dev@lucene.apache.org Subject: RE: [Lucene.Net] JIRA issues for Java Lucene changes In the time needed to create 10s of issues, half of the fixes could be done :) DIGY -Original Message- From: Lombard, Scott [mailto:slomb...@kingindustries.com] Sent: Wednesday, February 23, 2011 11:36 PM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] JIRA issues for Java Lucene changes Troy, I will start adding separate JIRA issues tonight. In the past do all the Java Lucene issues translate into .Net issues? Scott On Wed, Feb 23, 2011at 2:20 PM ,Troy Howard [mailto:thowar...@gmail.com] wrote: Scott, I would say the first task would be to collect all the Java changes up and create separate JIRA issues for each one. Thanks, Troy On Wed, Feb 23, 2011 at 9:16 AM, Lombard, Scott slomb...@kingindustries.com wrote: I am on vacation next week. So I won't be very helpful the next couple of days. I will be able take on some things for the 2.9.4 release. Are we going to break down the Java Lucene changes to individual items that need to be ported or is it going to be handled as one big task? Scott -Original Message- From: Troy Howard [mailto:thowar...@gmail.com] Sent: Wednesday, February 23, 2011 3:32 AM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] Lucene.Net Tasks due by 2/28 All, I've recently been updating JIRA a lot and that's causing a lot of noise on the dev list. Also, because of that noise, I fear that some of the more important details of those changes might be passing by unnoticed. Mostly, I'm trying to get the project cleaned up by the end of the month. The goal is that March will represent a month of building out our new infrastructure and creating our first new release as a team (2.9.4). To that end, I'd like to resolve some of the outstanding questions about tooling so we can get started building out solutions with those tools. Also, I'd like to see our new status and efforts announced publicly, but I'm hesitant to draw much attention to the project until the website is updated. Additionally, I'd like to take a moment to apologize a bit for moving at such a rapid pace. I realize this is not sustainable and could cause some people to feel alienated if they don't have the time or energy right this second to match that pace. I also feel a bit self-conscious and am concerned that I'm being a little to much 'me', and perhaps not enough 'we'. I have been taking a lot of liberty regarding the project direction, bypassing some opportunities for community discussion and voting, in the interests of pushing the project forward and catching up a bit of lost time. Once we get past this initial push, I hope that we can slow down a bit, and maintain a healthy forward-moving pace with plenty of time allotted for discussion, group decision making and voting. The Apache Way is the way this project will succeed and thrive, and that requires all of us. So, that said, the outstanding tasks, which we can hopefully complete by next Monday are: Troy Howard: LUCENENET-381 - Official release of Lucene.Net 2.9.2 Sergey Mirvoda: LUCENENET-398 - LUCENENET-391 Prepare the code for ingestion Michael Herndon: LUCENENET-400 - Evaluate tooling for continuous integration server Prescott Nasser: LUCENENET-379 - Clean up Lucene.Net website LUCENENET-379 / LUCENENET-403 - Improve site layout and design LUCENENET-379 / LUCENENET-402 - Update website to reflect current status and information LUCENENET-379 / LUCENENET-401 - Update website to be Apache CMS based Alex Thompson: LUCENENET-380 - Evaluate Sharpen as a port tool Does anyone feel less than confident about being able to complete those tasks on that schedule? Need any help? Want to change assignments? Anyone in the community want to get involved as a contributor on any of these tasks (or any of the open tasks in JIRA that are not listed here)? Sergey could probably use some help on Luke.Net. Prescott has a lot of work cut out for him on the website. Perhaps we should get the ball rolling on 2.9.4 task assignments for everyone else? Thanks, Troy This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or
RE: [Lucene.Net] JIRA issues for Java Lucene changes
We can take,for ex, a namespace like Lucene.Net.Util(+test cases) and create a single patch for all of the related issues. (This approach needs to work on svn history, not on issues) DIGY -Original Message- From: Lombard, Scott [mailto:slomb...@kingindustries.com] Sent: Thursday, February 24, 2011 12:14 AM To: lucene-net-dev@lucene.apache.org Subject: RE: [Lucene.Net] JIRA issues for Java Lucene changes You're probably right DIGY. I will take a look at issues and create JIRA issues where the complexity deems it appropriate. I will comment or patch otherwise. Scott -Original Message- From: Digy [mailto:digyd...@gmail.com] Sent: Wednesday, February 23, 2011 5:02 PM To: lucene-net-dev@lucene.apache.org Subject: RE: [Lucene.Net] JIRA issues for Java Lucene changes In the time needed to create 10s of issues, half of the fixes could be done :) DIGY -Original Message- From: Lombard, Scott [mailto:slomb...@kingindustries.com] Sent: Wednesday, February 23, 2011 11:36 PM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] JIRA issues for Java Lucene changes Troy, I will start adding separate JIRA issues tonight. In the past do all the Java Lucene issues translate into .Net issues? Scott On Wed, Feb 23, 2011at 2:20 PM ,Troy Howard [mailto:thowar...@gmail.com] wrote: Scott, I would say the first task would be to collect all the Java changes up and create separate JIRA issues for each one. Thanks, Troy On Wed, Feb 23, 2011 at 9:16 AM, Lombard, Scott slomb...@kingindustries.com wrote: I am on vacation next week. So I won't be very helpful the next couple of days. I will be able take on some things for the 2.9.4 release. Are we going to break down the Java Lucene changes to individual items that need to be ported or is it going to be handled as one big task? Scott -Original Message- From: Troy Howard [mailto:thowar...@gmail.com] Sent: Wednesday, February 23, 2011 3:32 AM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] Lucene.Net Tasks due by 2/28 All, I've recently been updating JIRA a lot and that's causing a lot of noise on the dev list. Also, because of that noise, I fear that some of the more important details of those changes might be passing by unnoticed. Mostly, I'm trying to get the project cleaned up by the end of the month. The goal is that March will represent a month of building out our new infrastructure and creating our first new release as a team (2.9.4). To that end, I'd like to resolve some of the outstanding questions about tooling so we can get started building out solutions with those tools. Also, I'd like to see our new status and efforts announced publicly, but I'm hesitant to draw much attention to the project until the website is updated. Additionally, I'd like to take a moment to apologize a bit for moving at such a rapid pace. I realize this is not sustainable and could cause some people to feel alienated if they don't have the time or energy right this second to match that pace. I also feel a bit self-conscious and am concerned that I'm being a little to much 'me', and perhaps not enough 'we'. I have been taking a lot of liberty regarding the project direction, bypassing some opportunities for community discussion and voting, in the interests of pushing the project forward and catching up a bit of lost time. Once we get past this initial push, I hope that we can slow down a bit, and maintain a healthy forward-moving pace with plenty of time allotted for discussion, group decision making and voting. The Apache Way is the way this project will succeed and thrive, and that requires all of us. So, that said, the outstanding tasks, which we can hopefully complete by next Monday are: Troy Howard: LUCENENET-381 - Official release of Lucene.Net 2.9.2 Sergey Mirvoda: LUCENENET-398 - LUCENENET-391 Prepare the code for ingestion Michael Herndon: LUCENENET-400 - Evaluate tooling for continuous integration server Prescott Nasser: LUCENENET-379 - Clean up Lucene.Net website LUCENENET-379 / LUCENENET-403 - Improve site layout and design LUCENENET-379 / LUCENENET-402 - Update website to reflect current status and information LUCENENET-379 / LUCENENET-401 - Update website to be Apache CMS based Alex Thompson: LUCENENET-380 - Evaluate Sharpen as a port tool Does anyone feel less than confident about being able to complete those tasks on that schedule? Need any help? Want to change assignments? Anyone in the community want to get involved as a contributor on any of these tasks (or any of the open tasks in JIRA that are not listed here)? Sergey could probably use some help on Luke.Net. Prescott has a lot of work cut out for him on the website. Perhaps we should get the
RE: [Lucene.Net] JIRA issues for Java Lucene changes
Instead of looking at issues, use TortoiseSVN's compare revision utility.
Some issues seem to be complex but patches are really simple. See the fix
for 2 of 103 files below
DIGY
Index: Constants.cs
===
--- Constants.cs (revision 1049646)
+++ Constants.cs (working copy)
@@ -70,7 +70,7 @@
return s.ToString();
}
- public static readonly System.String LUCENE_MAIN_VERSION =
Ident(2.9.2);
+ public static readonly System.String LUCENE_MAIN_VERSION =
Ident(2.9.4);
public static System.String LUCENE_VERSION;
static Constants()
Index: PriorityQueue.cs
===
--- PriorityQueue.cs(revision 1049646)
+++ PriorityQueue.cs(working copy)
@@ -92,7 +92,26 @@
// We allocate 1 extra to avoid if statement in top()
heapSize = 2;
else
- heapSize = maxSize + 1;
+{
+if (maxSize == Int32.MaxValue)
+{
+// Don't wrap heapSize to -1, in this case, which
+// causes a confusing NegativeArraySizeException.
+// Note that very likely this will simply then hit
+// an OOME, but at least that's more indicative to
+// caller that this values is too big. We don't +1
+// in this case, but it's very unlikely in practice
+// one will actually insert this many objects into
+// the PQ:
+heapSize = Int32.MaxValue;
+}
+else
+{
+// NOTE: we add +1 because all access to heap is
+// 1-based not 0-based. heap[0] is unused.
+heapSize = maxSize + 1;
+}
+}
heap = new System.Object[heapSize];
this.maxSize = maxSize;
-Original Message-
From: Lombard, Scott [mailto:slomb...@kingindustries.com]
Sent: Thursday, February 24, 2011 12:14 AM
To: lucene-net-dev@lucene.apache.org
Subject: RE: [Lucene.Net] JIRA issues for Java Lucene changes
You're probably right DIGY. I will take a look at issues and create JIRA
issues where the complexity deems it appropriate. I will comment or patch
otherwise.
Scott
-Original Message-
From: Digy [mailto:digyd...@gmail.com]
Sent: Wednesday, February 23, 2011 5:02 PM
To: lucene-net-dev@lucene.apache.org
Subject: RE: [Lucene.Net] JIRA issues for Java Lucene changes
In the time needed to create 10s of issues, half of the fixes could be
done
:)
DIGY
-Original Message-
From: Lombard, Scott [mailto:slomb...@kingindustries.com]
Sent: Wednesday, February 23, 2011 11:36 PM
To: lucene-net-dev@lucene.apache.org
Subject: [Lucene.Net] JIRA issues for Java Lucene changes
Troy,
I will start adding separate JIRA issues tonight. In the past do all the
Java Lucene issues translate into .Net issues?
Scott
On Wed, Feb 23, 2011at 2:20 PM ,Troy Howard [mailto:thowar...@gmail.com]
wrote:
Scott,
I would say the first task would be to collect all the Java changes up
and create separate JIRA issues for each one.
Thanks,
Troy
On Wed, Feb 23, 2011 at 9:16 AM, Lombard, Scott
slomb...@kingindustries.com wrote:
I am on vacation next week. So I won't be very helpful the next
couple
of days. I will be able take on some things for the 2.9.4 release. Are
we going to break down the Java Lucene changes to individual items that
need to be ported or is it going to be handled as one big task?
Scott
-Original Message-
From: Troy Howard [mailto:thowar...@gmail.com]
Sent: Wednesday, February 23, 2011 3:32 AM
To: lucene-net-dev@lucene.apache.org
Subject: [Lucene.Net] Lucene.Net Tasks due by 2/28
All,
I've recently been updating JIRA a lot and that's causing a lot of
noise on the dev list. Also, because of that noise, I fear that some
of the more important details of those changes might be passing by
unnoticed.
Mostly, I'm trying to get the project cleaned up by the end of the
month. The goal is that March will represent a month of building out
our new infrastructure and creating our first new release as a team
(2.9.4). To that end, I'd like to resolve some of the outstanding
questions about tooling so we can get started building out solutions
with those tools. Also, I'd like to see our new status and efforts
announced publicly, but I'm hesitant to draw much attention to the
project until the website is updated.
Additionally, I'd like to take a moment to
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998626#comment-12998626 ] Alex Thompson commented on LUCENENET-380: - That's worth a shot I guess. Forum thread I started: http://developer.db4o.com/Forums/tabid/98/aft/10503/Default.aspx Evaluate Sharpen as a port tool --- Key: LUCENENET-380 URL: https://issues.apache.org/jira/browse/LUCENENET-380 Project: Lucene.Net Issue Type: Task Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test Reporter: George Aroush Assignee: Alex Thompson Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, TestBufferedIndexInput.java, TestDateFilter.java This task is to evaluate Sharpen as a port tool for Lucene.Net. The files to be evaluated are attached. We need to run those files (which are off Java Lucene 2.9.2) against Sharpen and compare the result against JLCA result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Lucene.Net] [VOTE] Release Apache Lucene.Net 2.9.2-incubating-RC1
On 2011-02-23, Troy Howard wrote: Whenever we get our CI server setup, we should probably have a build task which checks for licensing in code files and inserts it if it's not there. Buildbot http://ci.apache.org/buildbot.html can be set up to create RAT reports, even for projects that use other CI options for their actual builds http://ci.apache.org/projects/. You can even check in a file containing the names of files that should be skipped because you know it won't and can't contain the license. I wouldn't recommend having a tool add the license automatically, maybe the file simply isn't licensed using the Apache Software License, maybe you'd make it useless if you added the license. Stefan
