All,
The recent discussions on this mailing list have shown a few things to be true:
- Lucene.Net is definitely still a thriving project with strong
leadership represented by George and DIGY
- The community surrounding the project is vocal, vibrant and filled
with ideas and motivation to help
- T
I agree with this idea completely. Standardizing the file format and
the query parser's syntax (ABNF? probably something similar exists
already since the parser is generated) would be a great start. Plus
some standards about "what criteria must a implementation of Lucene
meet to be valid?".. Obviou
Neal,
As you said, "If you're developing at the concept level the specific
language you use becomes unimportant. ".
This is exactly why we feel that working on this in C# is not a
problem. We feel that the language should not impede our ability to
contribute. If we develop some interesting or val
Grant,
Thanks for your considered response. Obviously, assuming that the
project continues to move forward, a change of status is not the end
of the world.
I supposed this is something that those of us who are not yet part of
ASF cannot grok due to lack of a deep understanding of how project
mana
xecuted
> code. Keeping a focus on making strong conversion tools as a community
> should help reduce the lag between a Java releases to a .Net releases. We
> then won't be waiting for one person to make the conversion.
>
> Scott
>
> -Original Message-
> From: Troy
Marco,
I agree with you on this front. I feel that the first tasks that a new
Lucene.Net team should focus on, in terms of development are:
- Fully automating a line-by-line port using a tool such as Sharpen.
This needs to become a commodity function requiring very little
development effort
- Bri
That is exactly what I would suggest. Sharpen looks like a great tool,
since you can customize it's behaviour. In fact, the only downside is
that you have to customize it's behaviour which requires a lot of
upfront work.
Thanks,
Troy
On Thu, Dec 30, 2010 at 11:42 AM, Prescott Nasser wrote:
>
>
gt; feel that I should just be a good c# programmer to help out.
>>
>> Would it not make more sense, given the fact that we want to reduce work and
>> make a quality product that we become more selective about *what* goes
>> through Sharpen and what can be hand-crafted? IE:
ome take extended
> vacations during the week of new years. (*shogatsu* or *oshogatsu) *is
> pretty popular in japan, Some people take extra days off to account for
> having to spend time with family during christmas etc.
>
>
> On Thu, Dec 30, 2010 at 2:51 PM, Troy Howard wrote:
&
ific
> classes?
>
> - Ben
>
> ------
>
>Troy Howard
> December 30, 2010 12:39 PM
>
> It's my opinion that we can basically commoditize an automated port
> which will fulfill the needs of the community, and allow the project
> to, at mi
Grant,
I'm working on the proposal and have come to the final section where I
must list a Champion and list of Mentors.
Can I put your name for Champion and possibly as a Mentor as well? Are
there any other folk out there willing to Mentor our project during
incubation? Should I instead wait for
Scott Lombard
Simone Chiaretta
Troy Howard
I would like to place an open request for any interested parties to
respond to this message with their request to be a Committer. For
people who are either on that list or for people who would like to be
added, please send a message explaining (briefly) wh
All,
Please review the draft proposal located at:
http://wiki.apache.org/incubator/Lucene.Net%20Proposal
If you'd like to make an edit feel free create an account and edit the
page as you see fit. I'd especially appreciate help with spelling and
grammar proofreading in that regard.
Regarding co
Sorry... I was in outer space with those dates.
To clarify, I'll submit the application on Tuesday, January 11th, 2011
which gives us exactly 12 days as a community to determine our
opinions, plans, develop our proposal and committer list.
Thanks,
Troy
On Thu, Dec 30, 2010 at 4:13 PM,
We are inheriting the outstanding issues facing the Lucene.Net project.
This includes remaining committed to providing a line-by-line port
that stays in sync with the Java Lucene releases.
The project is currently extremely behind schedule on this. The 2.9.2
code base, which is widely used and th
I have been impressed by Prescott Nasser's work in this area.
I would like to nominate him for managing documentation. That includes
leading the discussion on how to proceed with documentation.
One thing that is unclear to me at this point are the details of the
project website. I don't know how
I agree with the suggestion to follow the MS Coding standard. It's a
good general guideline. Specifically, I'd like to follow all
guidelines put forth in the book:
Framework Design Guidelines: Conventions, Idioms, and Patterns for
Reusable .NET Libraries by Krzysztof Cwalina and Brad Abrams
http:/
al Stage: Backwards Compatibility / Support
>> Date: Sun, 2 Jan 2011 19:03:25 +0200
>>
>> > The 3.0.X ports should be 100% Sharpen
>> Why?
>> What about other alternatives?
>>
>> Lucene.java 3.0.3 ==> .Net Conversion Samples (
>> http://people.apache.org/
To: lucene-net-dev@lucene.apache.org
>> > Subject: RE: Proposal Stage: Backwards Compatibility / Support
>> > Date: Sun, 2 Jan 2011 19:03:25 +0200
>> >
>> > > The 3.0.X ports should be 100% Sharpen
>> > Why?
>> > What about other altern
;
> -Grant
>
> On Dec 30, 2010, at 6:32 PM, Troy Howard wrote:
>
>> Grant,
>>
>> I'm working on the proposal and have come to the final section where I
>> must list a Champion and list of Mentors.
>>
>> Can I put your name for Champion and p
t; Lucene.java 3.0.3 ==> .Net Conversion Samples (
> http://people.apache.org/~digy/Lucene.Net.3.0.3.zip )
>
> DIGY
>
>
>
> -Original Message-
> From: Troy Howard [mailto:thowar...@gmail.com]
> Sent: Saturday, January 01, 2011 1:58 AM
> To: lucene-net-dev@l
.org/site/index.html
http://sling.apache.org/site/index.html
I think it's clean, modern, and versatile. The Maven built sites look
ok as well, but not as pretty. I'm not a fan of Forrest.
Thanks,
Troy
On Fri, Dec 31, 2010 at 4:24 PM, Troy Howard wrote:
> I have been impressed by Pr
All,
Now that we've moved past the proposal stage and defined our Initial
Committers list, I'd like to address the topic of how to be a
Contributor to Lucene.Net.
Some quick things to note upfront about roles. Previously I made a
point of distinguishing between Contributors and Committers at ASF.
Apache has a number of CI options available... For details, see:
http://ci.apache.org/
I'd suggest Hudson.
Regarding Mono support, I think providing a MonoDevelop compatible
solution file, and testing builds in at least one standard Linux
environment will be necessary. I'd suggest Ubuntu 10.4 or
I'm on the fence about IKVM.
It has some significant benefits and some significant drawbacks:
Benefits:
- Allows us to get to a "commoditized" line-by-line .NET DLL in the
fastest and easiest manner. No porting.
- Reasonable performance profile
- Well tested Java environment equivalence
Drawback
It's unclear at this point. My recommendation in the proposal was the
move it over, because at that time the Wiki was empty.
Either way, I believe the page syntax should be the same, and so
moving the pages over wouldn't be too terrible.
Thanks,
Troy
On Sat, Jan 29, 2011 at 2:40 PM, Prescott Na
,
Troy
On Sat, Jan 29, 2011 at 3:10 PM, Troy Howard wrote:
> It's unclear at this point. My recommendation in the proposal was the
> move it over, because at that time the Wiki was empty.
>
> Either way, I believe the page syntax should be the same, and so
> moving the pages
The QueryParser has those strings hardcoded with no facility for
internationalization. To change them, you'd have to change the values
of the string constant in QueryParser.cs
Specifically, QueryParser.cs, lines 181/182:
public static readonly Operator OR = new Operator("OR");
public static reado
So, currently we are only setup for working in the staging
environment. Once we are ready to publish, we'll need to enter a new
JIRA ticket to the infrastructure project and ask for the site to be
set up for publishing. Once that's done, we will be able to
self-publish whenever we'd like either thr
I outlined a rough and rather arbitrary roadmap in the staging site
content with basic timeline. It was my intention to go back and create
the appropriate releases in JIRA, schedule them, create issues that
aren't in there yet, and assign everything to a specific release.
I agree with Prescott's a
I'm not terribly familiar with JIRA. Is it possibile that we can have
more than one person as administrator?
I'd like to be able to work on the Roadmap, and start doing some
scheduling, but currently don't have enough permissions to make those
kinds of changes.
DIGY - As admin can you grant admin
All,
Following up on Scott's post asking about JIRA issues and our
development road map, I've put together a more detailed idea of how
we could divide work, schedule releases, and clean up the backlog.
There will be at least four main areas of work to address in the
upcoming months:
- Project Mai
Yes. If you look at the milestone dates on those two tracks of development:
Lucene.Net 2.9.2 Binary release (02/28/2011)
Create Production System, 2.9.2 compatible (03/28/2011)
Lucene.Net 2.9.4 Source/Binary release (03/28/2011)
Create Production System, 2.9.4 compatible (04/25/2011)
The porting
Aaron,
That's awesome!
Would you be opposed to us importing this in the Lucene.Net
respository, and maintaining it here?
Thanks,
Troy
On Fri, Feb 18, 2011 at 1:47 AM, Aaron Powell wrote:
> A while ago I started working on a port of Luke for .NET, and a colleague of
> mine also gave a bit of
; aaron.l.powell | MSN: aaz...@hotmail.com
>>
>> -Original Message-
>> From: Troy Howard [mailto:thowar...@gmail.com]
>> Sent: Friday, 18 February 2011 8:51 PM
>> To: lucene-net-dev@lucene.apache.org
>> Cc: Aaron Powell
>> Subject: Re: Luke.Net
Ayende,
I opened a JIRA issue for this here:
https://issues.apache.org/jira/browse/INFRA-3463
Thanks,
Troy
On Wed, Feb 16, 2011 at 1:23 PM, Ayende Rahien wrote:
> Off topic, can we get a [Lucene.NET] prefix for messages to the list?
>
> On Wed, Feb 16, 2011 at 11:05 PM, Prescott Nasser
> wro
Pending resolution of the legal issues around ingesting the code into
Lucene.Net, I've created a public fork of Luke.Net on bitbucket as a
staging area to prepare the code for ingestion. Sergey will be working
on it there.
Thanks,
Troy
On Fri, Feb 18, 2011 at 6:23 AM, Stefan Bodewig wrote:
> On
It's a common practice for developers to create a branch to work on a
new feature, then merge that branch back into trunk later when the
changes are complete, then delete the branch.
The goal is to ensure that incremental commits, performed now against
the branch instead of trunk, don't leave trun
a central repo later.
Thanks,
Troy
On Fri, Feb 18, 2011 at 1:52 PM, Digy wrote:
> But I would prefer do the same thing on my own local copy and create a patch
> for trunk.
>
> Thanks,
> DIGY
>
> -Original Message-
> From: Troy Howard [mailto:thowar...@gmail.com
My opinion is that multiple solution files is a perfectly reasonable
middle ground. I like to place all of the solution files in a single
'Build' directory, instead of in the root folder of different
directory branches...
Suppose we had: \trunk\C#\src\Build\
- Lucene.Net Core.sln: Compiles only t
Disclaimer: Troy's Personal Opinions (tm) which may be controversial,
will be found below
Regarding the idea of 'feature branches', I guess I should make it
clear that I personally don't agree with this workflow in SVN.
This is completely appropriate for Mercurial or Git, because they were
design
Stefan/DIGY,
Have either of you gone through the process of making a signed release
yourselves? I've been reading over the documentation, and well..
That's a lot of documentation. It's hard to tell how much of this is
relevant.
I'd like to get myself set up to to do this but it seems a bit
comple
+1 for not supporting bugs in earlier releases.
The answer to those questions should be 'upgrade to the latest
release. If you still have a problem with the latest release, let us
know'.
On Fri, Feb 18, 2011 at 9:43 PM, Prescott Nasser wrote:
>
> Unless they affect current release, I think we
All,
The mailing lists have been updated to include a subject line prefix of
[Lucene.Net].
Please update any mail filters you may have that relate.
Thanks,
Troy
n is kind of all over
the place. It discusses so many edge cases and different methods for
doing this that it's hard to know what the correct one is. I might be
missing something. Do you mind breaking it down for me in a very
simple step by step manner?
Thanks,
Troy
On Fri, Feb 18, 2011 at 8:
m GAC) should be handled by Lucene.Net.
> At the end, all Lucene.Net users are developers.
>
> DIGY
>
>
> -Original Message-
> From: Troy Howard [mailto:thowar...@gmail.com]
> Sent: Monday, February 21, 2011 7:08 PM
> To: lucene-net-dev@lucene.apache.org
> Subj
On Mon, Feb 21, 2011 at 9:38 PM, Stefan Bodewig wrote:
> On 2011-02-21, Troy Howard wrote:
>
>> Stefan - You indicated that the Apache signing process is
>> straightforward and simple, but the documentation is kind of all over
>> the place.
>
> I've never read any
All,
I'm happy to announce that Lucene.Net 2.9.2-incubating-RC1 is
available and ready for your testing and voting.
Release candidate artifacts:
http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC1/dist/
SVN tag revision:
http://svn.apache.org/repos/asf/incubator/lucene.net/tags/L
move our past release artifacts there?
Thanks,
Troy
On Tue, Feb 22, 2011 at 9:08 PM, Stefan Bodewig 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
&
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 - Of
nough '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
>> > lo
ill 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:tho
Stefan,
I'm pretty close to finishing a second release candidate... Been busy
today/yesterday.
Thanks,
Troy
On Fri, Feb 25, 2011 at 1:25 AM, Stefan Bodewig wrote:
> On 2011-02-23, Stefan Bodewig wrote:
>
>> Not only cosmetic:
>
>> * The NOTICE file contains a bad copyright year and doesn't tal
No problem. Updated them, and a new release candidate is ready (posting now).
Thanks,
Troy
On Fri, Feb 25, 2011 at 3:17 AM, Stefan Bodewig wrote:
> On 2011-02-25, wrote:
>
>> Added app.configs (missing from previous commit)
>
> They need licenses as well. Sorry to be a PITA.
>
> Stefan
>
All,
This vote is being closed as not passing due to the valid issues Stefan raised.
Thanks,
Troy
On Tue, Feb 22, 2011 at 3:35 PM, Troy Howard wrote:
> All,
>
> I'm happy to announce that Lucene.Net 2.9.2-incubating-RC1 is
> available and ready for your testing and vo
All,
I'm happy to announce that Lucene.Net 2.9.2-incubating-RC2 is
available and ready for your testing and voting.
Release candidate artifacts:
http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC2/dist/
SVN tag revision:
http://svn.apache.org/repos/asf/incubator/lucene.net/tags/L
ecognized. MSBuild can only read solution files between versions 7.0
> and 9.0, inclusive.
>
>
> - Neal
>
>
> -----Original Message-
> From: Troy Howard [mailto:thowar...@gmail.com]
> Sent: Friday, February 25, 2011 5:56 AM
> To: lucene-net-dev@lucene.apa
We should probably include documentation somewhere that building
requires either MsBuild from 3.5 or higher .NET framework install or a
version of VS2010 (Express works fine).
Thanks,
Troy
On Fri, Feb 25, 2011 at 7:49 AM, Troy Howard wrote:
> It's a VS2010 solution file. What version
All,
I updated the .src zip and associated checksums/signatures at:
http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC2/dist/
Hopefully this one will pass the licensing validation! I think I got
them all this time..
Thanks,
Troy
n Fri, Feb 25, 2011 at 12:20 PM, Digy wrote:
> What about this source tree?
> RC2
> build
> contrib
> core
> Lucene.Net
> Test
> demo
>
> "src" doesn't mean anything since other dirs contain sources as well.
>
&
I prefer it that way as well, but the current setup has one for each
project. I guess it makes sense for the Contrib projects because the
folks who developed them probably worked on them in isolation from the
rest of Lucene.Net.
Anyway, I'd be happy to have less files to maintain. ;)
If they don'
ut any previous
> warnings(although I understand Troy's arguments). Now, I have to reorganize
> all my local works.
>
> DIGY
>
> -Original Message-
> From: Troy Howard [mailto:thowar...@gmail.com]
> Sent: Saturday, February 26, 2011 1:06 AM
> To: lucene-net-dev
+1 to all suggestions. Hudkins is my new favourite word. ;)
One quick concern I have, is how much of the things listed are already
available on the Apache hudson server? A lot of this is .NET specific, so
unlikely that it will already be available. We'll have to request that ASF
Infra team install
+1 for RC release.
On Fri, Feb 25, 2011 at 9:37 AM, Troy Howard wrote:
> All,
>
> I updated the .src zip and associated checksums/signatures at:
>
> http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC2/dist/
>
> Hopefully this one will pass the licensing vali
will become an official ASF Incubator release.
Thanks,
Troy
On Fri, Feb 25, 2011 at 12:29 PM, Stefan Bodewig wrote:
> On 2011-02-25, Troy Howard wrote:
>
>> I updated the .src zip and associated checksums/signatures at:
>
> I have verified the bin zip is still the same th
Björn,
As far as a release schedule for a 3.X release goes.. Realistically,
it's not likely to be ready until sometime in the later half of this
year.
As you found in the blog article mentioned, the project was going
through some difficult times last year. Since that time, the project
has seen a
I'd love to help with the CSS/graphics, though right at the moment I'm
kind of swamped with day job work. It might be hard to find time to
devote to the Lucene.Net site until next week.
Anyone else have time/skills to apply?
NOTE: This does not have to be a committer. This is a great
opportunity
This sounds like a great opportunity.
However airfare, roundtrip from Portland, OR is ~$900; A little
expensive. So, I'm a solid 'maybe'.
Thanks,
Troy
On Wed, Mar 2, 2011 at 9:19 PM, Stefan Bodewig wrote:
> Hi all,
>
> I think most people around here are US based, but is anybody going to
> Kno
I went ahead and applied for travel assistance.
On Wed, Mar 2, 2011 at 10:12 PM, Troy Howard wrote:
> This sounds like a great opportunity.
>
> However airfare, roundtrip from Portland, OR is ~$900; A little
> expensive. So, I'm a solid 'maybe'.
>
> Thanks,
&g
Prescott,
I started a thread called 'Proposed Roadmap' a while back. It's here:
http://s.apache.org/9Ov
We just finished a new official release, and I will be announcing it
either today or tomorrow (I was waiting for the mirror sites to get
updated before announcing it). It's located here:
http
All,
We'd like to update the project directory structure/layout.
See below for a proposed layout. I've also uploaded an example which
you can navigate at:
http://people.apache.org/~thoward/Lucene.Net/directory-structure-example
NOTE: This will not build!! I just put things in the appropriate
pl
Another good way to put this:
Google is an application which crawls and indexes the internet and
provides search functionality to end users. It uses domain specific
logic to perform it's ranking to improve relevance.
Lucene and Lucene.Net is a library, which allows end users to build
full text se
Hah! You beat me to it! You edited the wiki while I was typing up some
stuff in a text editor for that purpose.
I like your version of the report better.. ;)
Good job!
Thanks,
Troy
On Mon, Mar 7, 2011 at 6:43 PM, Prescott Nasser wrote:
>
> thanks for the nudge - I've updated this section
>
>
>
w Directory Layout for Project
>> >
>> > +1
>> >
>> > just a question though. for cmd/bat//sh files for letting people
>> executing
>> > the build or just executing other tools from the command line, would
>> those
>> > have a place in /
-dev@lucene.apache.org
>> > > CC: thowar...@gmail.com
>> > > Subject: Re: [Lucene.Net] [VOTE] New Directory Layout for Project
>> > >
>> > > +1
>> > >
>> > > just a question though. for cmd/bat//sh files for letting people
>&g
I like the CTR workflow, but ensure that all commits have an
associated JIRA item in the commit log so that it's tracked in JIRA
correctly via the commits tab.
I also recently asked Infra to set us up with ReviewBoard (see
reviews.apache.org)... However this tool is focused on RTC style
workflow.
I have had success asking questions in #asfinfra . Maybe they can explain.
On Saturday, March 19, 2011, Prescott Nasser wrote:
>
> I added the fix to check if path is null - now of course when updating via
> the cms javascript on hte site, the path is null, so the tagline gets set to
> the defa
I agree that it should not throw an overflow exception. That's not
very helpful for debugging.
The valid range of that parameter is essentially [0...
Int32.MaxValue-1].. That's because it needs one extra slot in it's
internal array, beyond the max size for juggling values during sort.
The exceptio
Ruben,
To unsubscribe from the mailing list send a message to:
lucene-net-dev-unsubscr...@lucene.apache.org
Thanks,
Troy
On Mon, Mar 28, 2011 at 8:09 PM, Ruben Pierich wrote:
>
> Unsubscribe.
>
>> Date: Mon, 28 Mar 2011 21:35:05 +
>> From: j...@apache.org
>> To: lucene-net-dev@lucene.apac
t; Sorry, no binaries. You can download the source from
>> https://svn.apache.org/repos/asf/incubator/lucene.net/trunk/C#/src/Lucene.Net
>>
>> DIGY
>>
>> On Tue, Apr 5, 2011 at 12:12 AM, Wyatt Barnett
>> wrote:
>>
>>> Actually about to dive int
Apologize. I got a bit derailed. Will be commiting today.
On Apr 16, 2011 2:20 PM, "Prescott Nasser" wrote:
>
>
> Hey Troy any status update on the new structure? I'm hesistant to do
updates since I know you're going to be modifying it all shortly
>
> ~P
>
o same.
Please pull down the latest revision and validate these changes. If all goes
well, I'll delete the old directory structure (everything under the 'C#'
directory).
Thanks,
Troy
On Sat, Apr 16, 2011 at 3:42 PM, Troy Howard wrote:
> Apologize. I got a bit derailed. Will be c
I considered going, but the price was a bit high.
I AM going to the Apache Knockree retreat in May... My request for travel
assistance was granted! Yippee!
Anyone else going?
Thanks,
Troy
On Thu, Apr 21, 2011 at 1:37 PM, Wyatt Barnett wrote:
> Comerade?
>
> Seems like there is a Lucene confer
Using var is wonderful and great. We'll hopefully do doing a lot of
refactoring in the near future. var makes refactoring easier.
I think we've committed fairly strongly to moving past 2.0 support. AFAIK
the current trunk won't build under 2.0 anyhow (or am I mistaken, DIGY used
HashSet in a recen
Are you working with VS2010 Express? Or one of the full versions?
If you're using Express, unfortunately, it's default settings are a bit
confusing. In the create new project dialog, the 'normal' field for project
directory is not displayed, only one for name. To enable this, you need to
go to 'To
I was waiting for a round of testing/consensus regarding the trunk before
deleting the old directory tree under C#.
I suppose it's been enough time, and I'll just delete/commit that.
Thanks,
Troy
On Sun, May 8, 2011 at 12:16 AM, Prescott Nasser wrote:
>
> I'd be happy too - but I haven't looke
All,
I'll be attending the Apache Retreat in Knockree next week (5/13-5/16). I
was thinking it would be fun to arrange a Lucene.Net Hackathon for the same
time frame. Even if you can't go to the event, we can hack together in a
distributed fashion. ;)
Hackathons are usually focused on particular
Re: "I'm not sure if there is a coding difference between the C# stuff and
the other directory stuff."
There are a few minor code changes in the new branch vs the C# branch, but
those are things like framework target, copyright notices, etc.. I didn't
change code significantly, and unit tests stil
ing in IL level. So, I don't see a case to vote.
> If you think the code will be easier to read, use it. If not, don't.
>
> DIGY
>
> -Original Message-
> From: Troy Howard [mailto:thowar...@gmail.com]
> Sent: Monday, May 09, 2011 10:54 PM
> To: lucene-net-de
Michael,
That worked!
I'm in the process of making a wiki page for the event now.
Thanks,
Troy
On Mon, May 9, 2011 at 1:38 PM, Michael Herndon
wrote:
>
> log out and log back in and verify permission changes.
>
> On Mon, May 9, 2011 at 4:22 PM, Troy Howard wrote:
>
>
4g is somewhere between 2.9.4 & 3.0.3(more close to 3.0.3)
>
> DIGY
>
> -Original Message-
> From: Troy Howard [mailto:thowar...@gmail.com]
> Sent: Monday, May 09, 2011 11:54 PM
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: [Lucene.Net] VOTE: .NET 2.0
Indeed... 2.9.4g it is!
"G" for Generics should be easy to remember.
On Mon, May 9, 2011 at 2:27 PM, Digy wrote:
> It is used already.
>
> https://issues.apache.org/jira/browse/LUCENE/fixforversion/12315914
>
> DIGY
>
> -Original Message-
> From: Troy
gt; they are all the same CLR
>
> Aaron Powell
> MVP - Internet Explorer (Development) | Umbraco Core Team Member | FunnelWeb
> Team Member
>
> http://apowell.me | http://twitter.com/slace | Skype: aaron.l.powell |
> MSN: aaz...@hotmail.com
>
> -Original Message-
Here's the wiki page:
https://cwiki.apache.org/confluence/x/Go6OAQ
Thanks,
Troy
On Mon, May 9, 2011 at 1:59 PM, Troy Howard wrote:
> Michael,
>
> That worked!
>
> I'm in the process of making a wiki page for the event now.
>
> Thanks,
> Troy
>
>
&
-- Forwarded message --
From: "Gavin McDonald"
Date: Jun 6, 2011 1:02 AM
Subject: Travel Assistance applications now open for ApacheCon NA 2011
To:
The Apache Software Foundation (ASF)'s Travel Assistance Committee (TAC) is
now accepting applications for ApacheCon North America 2
and it's hard for me to keep from worrying if there would
> need to be a sacrifice at some point to keep the project concentrated
> enough
> to remain viable. While the model of open source is such that *anyone* can
> contribute, this very mechanism can also lead to projects that ar
h the trunk. It need not be an offical release and can
> live in branch as a PoC.
>
>
> As a result, I got bored to listen to "this should be done that way". What
> I want to see is "I did it that way, should we continue with this".
>
> DIGY
>
&g
oy,
> > I also don't understand why do you wait for 2.9.4g? It is a *branch* and
> > has nothing to do with the trunk. It need not be an offical release and
> > can live in branch as a PoC.
> >
> >
> > As a result, I got bored to listen to "this should be d
; contrib or in branch. All of the approaches can live side by side happily
> in
> > the Lucene.Net repository.
> >
> > Troy,
> > I also don't understand why do you wait for 2.9.4g? It is a *branch* and
> > has nothing to do with the trunk. It need not be a
> > >
> > > >
> > > >
> > > > ** Asset.Throws needs to replace stuff like the following. We should
> > also
> > > > be checking the messages for exceptions and make sure they make sense
> > and
> > > > can help users
1 - 100 of 186 matches
Mail list logo
