Steven Rowe wrote:
"2.1" is much more likely to be the label used for the next release than
"2.0.1".
The roadmap in Jira shows 21 issues scheduled for 2.0.1. If there is in
fact no intent to merge these into the 2.0 branch, these should probably
be retargetted for 2.1.0, and the 2.0.1 versio
when 2.0.1 will be released will help me plan things out.
Regards,
-- George Aroush
-Original Message-
From: George Aroush [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 12, 2006 12:07 AM
To: java-dev@lucene.apache.org
Subject: Lucene 2.0.1 release date
Hi folks,
What's th
George Aroush wrote:
> From your email, I take it that even for the Java folks, they can't
> accumulate the list of files that make up 2.0.1. Am I right?
There has never been and likely will never be a 2.0.1 release.
"2.0.1", "2.1" -- these are labels for *potential* future releases.
"2.1" is m
org
Subject: Re: Lucene 2.0.1 release date
George,
You may want to subscribe to java-dev or just look through the java-dev
archives to see how Lucene releases come about. Let me try re-enacting it.
dev 1: What do people think about a X.Y release?
group: Sure, why not, looks like we have enough ch
: The point is that releases are not planned ahead of time, so we can
: never tell which files that have been modified between, say, X.Y and
: X.Y.Z release. We know that only when the release is made. In short,
that's not entirely true ... it's very easy to determine exactly what has
changed b
can't port in "real-time", you have to wait for the release to be made, and
then start work on your new release.
Otis
- Original Message
From: George Aroush <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Wednesday, October 25, 2006 9:40:39 PM
Subject: RE:
SVN.)
Regards,
-- George
-Original Message-
From: Steven Parkes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 17, 2006 11:45 AM
To: java-user@lucene.apache.org
Subject: RE: Lucene 2.0.1 release date
I think the idea is that 2.0.1 would be a patch-fix release from the branch
created
EMAIL PROTECTED]
Sent: Sunday, October 15, 2006 5:15 PM
To: java-user@lucene.apache.org
Subject: RE: Lucene 2.0.1 release date
Thanks for the reply Otis.
I looked at the CHANGES.txt file and saw quit a bit of changes. For my
port
from Java to C#, I can't rely on the trunk code as it is (
allowing a bit more instability in trunk. That is, if the community
wants that.
Food for thought and/or discussion?
-Original Message-
From: George Aroush [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 15, 2006 5:15 PM
To: java-user@lucene.apache.org
Subject: RE: Lucene 2.0.1 release date
point.
Regards,
-- George Aroush
-Original Message-
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 15, 2006 12:41 AM
To: java-user@lucene.apache.org
Subject: Re: Lucene 2.0.1 release date
I'd have to check CHANGES.txt, but I don't think that many bugs
.apache.org; java-user@lucene.apache.org
Sent: Saturday, October 14, 2006 10:32:47 AM
Subject: RE: Lucene 2.0.1 release date
Hi folks,
Sorry for reposting this question (see original email below) and this time
to both mailing list.
If anyone can tell me what is the plan for Lucene 2.0.1 release,
ucene.apache.org
Sent: Saturday, October 14, 2006 10:32:47 AM
Subject: RE: Lucene 2.0.1 release date
Hi folks,
Sorry for reposting this question (see original email below) and this time
to both mailing list.
If anyone can tell me what is the plan for Lucene 2.0.1 release, I would
appreciate it very m
be released will help me plan things out.
Regards,
-- George Aroush
-Original Message-
From: George Aroush [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 12, 2006 12:07 AM
To: java-dev@lucene.apache.org
Subject: Lucene 2.0.1 release date
Hi folks,
What's the plan for Lucene
13 matches
Mail list logo
