+1 for releasing 2.1 soon.

I hope to get explicit commits (LUCENE-710) working, which has a tiny
file format change, and LUCENE-773 (deprecate FSDirectory.getDirectory
methods that take a create arg) completed soon, so we can get them
into 2.1, if possible.

Also +1 on more frequent releases after 2.1!

Mike

Otis Gospodnetic wrote:
Same here.  As soon as the file format changes settle down.

Otis

----- Original Message ----
From: Grant Ingersoll <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Tuesday, January 16, 2007 12:26:43 PM
Subject: Re: Lucene 2.1, soon

+1

Was thinking the same thing this morning. The changes.txt 2.1 section is getting quite long.

On Jan 16, 2007, at 12:16 PM, Yonik Seeley wrote:

Lucene 2.1 has been a long time in coming, but I think we should plan
on making a release when the file format changes settle down.

After that, I think we should start making more frequent releases,
which should make make many people's lives easier by
1) give people something more recent to work from w/o having to pick a
trunk version themselves.
2) make it easier to declare the trunk developmental, so developers
only need to be concerned with backward compatibility between actual
releases.

-Yonik

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------
Grant Ingersoll
Center for Natural Language Processing
http://www.cnlp.org

Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/ LuceneFAQ



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to