On Aug 25, 2008, at 2:18 PM, Chris Hostetter wrote:
: OK, so how about we upgrade Lucene again and then we set a freeze
date for
: Wednesday, Aug. 27 of 9 AM EDT (since that's my time zone, and I'm
the one
: calling it :-) )
Grant, Just to clarify.
you want to:
1) freeze the *trunk* o
Yonik Seeley wrote:
> Given that there are backward compat concerns with
> https://issues.apache.org/jira/browse/LUCENE-1142
> perhaps we should update Lucene again before a release?
>
As the maintainer of the Debian solr package, I would be interested to
know whether solr 1.3 will be compatible
: OK, so how about we upgrade Lucene again and then we set a freeze date for
: Wednesday, Aug. 27 of 9 AM EDT (since that's my time zone, and I'm the one
: calling it :-) )
Grant, Just to clarify.
you want to:
1) freeze the *trunk* on the 27th
2) focus on bug fixes and documentation improv
: The idea of putting new issues in 1.3.1 has been tossed around a few times on
: this list in the last few weeks. I'm not sure how other people feel about
: this, but in my mind, 1.X.Y and 1.X.Z releases should be feature-identical,
: with later releases only containing bugfixes. If we have a b
: Aren't we going to create a branch for this? If yes, why not upgrade lucene
: jars and freeze right now and release on 1st September? :-)
release branches are created, but durring the days leading up to a release
it's a good idea to refrain from doing too much work on the trunk:
1) it makes
3)
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Erik Hatcher <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Monday, August 25, 2008 10:06:46 AM
Subject: Re: 1.3 status
On Aug 25, 2008, at 9:48 AM, Yonik Seeley wrote:
Gi
I was thinking we might want a day or two on the new Lucene and also
that not everyone is reading this thread immediately, so we need to
give them time to react. But, yeah, we can create the branch today,
if that's what people want. Yonik, do you want to do the Lucene
upgrade (you're gett
On Mon, Aug 25, 2008 at 8:55 PM, Grant Ingersoll <[EMAIL PROTECTED]>wrote:
> OK, so how about we upgrade Lucene again and then we set a freeze date for
> Wednesday, Aug. 27 of 9 AM EDT (since that's my time zone, and I'm the one
> calling it :-) )
Aren't we going to create a branch for this? If
To: solr-dev@lucene.apache.org
> Sent: Monday, August 25, 2008 11:20:57 AM
> Subject: Re: 1.3 status
>
> On Mon, Aug 25, 2008 at 8:23 PM, Grant Ingersoll wrote:
>
> >
> > In Lucene Java, we typically freeze for 10 days, during which only
> > blockers and documentation patches ar
OK, so how about we upgrade Lucene again and then we set a freeze date
for Wednesday, Aug. 27 of 9 AM EDT (since that's my time zone, and I'm
the one calling it :-) )
-Grant
On Aug 25, 2008, at 11:20 AM, Shalin Shekhar Mangar wrote:
On Mon, Aug 25, 2008 at 8:23 PM, Grant Ingersoll
<[EMAI
On Mon, Aug 25, 2008 at 8:23 PM, Grant Ingersoll <[EMAIL PROTECTED]>wrote:
>
> In Lucene Java, we typically freeze for 10 days, during which only
> blockers and documentation patches are allowed to be committed. I'd be fine
> w/ 7, but what's 3 more days, right?
>
Thanks for the info Grant.
I'
On Aug 25, 2008, at 10:30 AM, Shalin Shekhar Mangar wrote:
+1 for Lucene upgrade
+1 for a release candidate.
I think the newer issues can make it to 1.3.1 easily. We don't need
to halt
1.3 for them.
A general question -- how long does a Release Candidate phase lasts?
In Lucene Java, we
lt;[EMAIL PROTECTED]>
> > To: solr-dev@lucene.apache.org
> > Sent: Monday, August 25, 2008 10:06:46 AM
> > Subject: Re: 1.3 status
> >
> >
> > On Aug 25, 2008, at 9:48 AM, Yonik Seeley wrote:
> > > Given that there are backward compat concerns with
>
t; Sent: Monday, August 25, 2008 10:06:46 AM
> Subject: Re: 1.3 status
>
>
> On Aug 25, 2008, at 9:48 AM, Yonik Seeley wrote:
> > Given that there are backward compat concerns with
> > https://issues.apache.org/jira/browse/LUCENE-1142
> > perhaps we should update Lucene again before a release?
>
> +1
>
> Erik
On Aug 25, 2008, at 9:48 AM, Yonik Seeley wrote:
Given that there are backward compat concerns with
https://issues.apache.org/jira/browse/LUCENE-1142
perhaps we should update Lucene again before a release?
+1
Erik
Given that there are backward compat concerns with
https://issues.apache.org/jira/browse/LUCENE-1142
perhaps we should update Lucene again before a release?
-Yonik
On Mon, Aug 25, 2008 at 9:02 AM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> So, what's our status? It appears everything is closed
So, what's our status? It appears everything is closed. Do people
feel comfortable w/ where we are at? There has been a whole flurry of
changes in recent weeks (let's not do that again right before a
release, eh?)
Shall I go forward w/ creating some a release candidate?
-Grant
gust 19, 2008 3:06:27 PM
Subject: Solr 1.3 Status, Lucene Status was Re: [jira] Commented:
(SOLR-697) Update Lucene jar before 1.3 release
I'm not sure where I stand on waiting for Lucene 2.4. It's at
least a
month away in my mind anyway due to the number of issues on it and
Lucen
- Original Message
> From: Grant Ingersoll <[EMAIL PROTECTED]>
> To: solr-dev@lucene.apache.org
> Sent: Tuesday, August 19, 2008 3:06:27 PM
> Subject: Solr 1.3 Status, Lucene Status was Re: [jira] Commented: (SOLR-697)
> Update Lucene jar before 1.3 release
>
> I&#x
I'm not sure where I stand on waiting for Lucene 2.4. It's at least a
month away in my mind anyway due to the number of issues on it and
Lucene's built in 10-day code freeze. I think after this release of
Solr, we will likely have a 1.3.1 release fairly soon to fix issues
that arise. Of
20 matches
Mail list logo
