1.3 status
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
Re: 1.3 status
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. 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 >
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
Re: 1.3 status
+1 for Lucene upgrade +1 for a release (I *think* none of the recent SOLR-7** issues have to go in 1.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: > > 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
Re: 1.3 status
+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? On Mon, Aug 25, 2008 at 7:51 PM, Otis Gospodnetic < [EMAIL PROTECTED]> wrote: > +1 for Lucene upgrade > +1 for a release (I *think* none of the recent SOLR-7** issues have to go > in 1.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: > > > 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 > > -- Regards, Shalin Shekhar Mangar.
Re: 1.3 status
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 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? -Grant
Re: 1.3 status
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've just committed another (small) issue but I promise this will be the last one from my side for 1.3. -- Regards, Shalin Shekhar Mangar.
Re: 1.3 status
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 <[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've just committed another (small) issue but I promise this will be the last one from my side for 1.3. -- Regards, Shalin Shekhar Mangar.
Re: 1.3 status
Grant, if you have time to make the RC today, we could run it until next weekend and have the 1.3 released on Monday. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: Shalin Shekhar Mangar <[EMAIL PROTECTED]> > 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 are allowed to be committed. I'd be fine > > w/ 7, but what's 3 more days, right? > > > > Thanks for the info Grant. > > I've just committed another (small) issue but I promise this will be the > last one from my side for 1.3. > > -- > Regards, > Shalin Shekhar Mangar.
Re: 1.3 status
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 yes, why not upgrade lucene jars and freeze right now and release on 1st September? :-) We can continue to work (and commit) on 1.4 issues on the trunk without stopping our hands. I'm planning to dedicate some time to work on the replication patches this week. -- Regards, Shalin Shekhar Mangar.
Re: 1.3 status
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 getting so good at it) and then we can create the branch? I can tell you now I'm not doing the release over the Labor day weekend, as I plan on minimizing my labor... On Aug 25, 2008, at 11:31 AM, Shalin Shekhar Mangar wrote: 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 yes, why not upgrade lucene jars and freeze right now and release on 1st September? :-) We can continue to work (and commit) on 1.4 issues on the trunk without stopping our hands. I'm planning to dedicate some time to work on the replication patches this week. -- Regards, Shalin Shekhar Mangar.
Re: 1.3 status
+1 for 1.3 RC. 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 bunch of cool features we want to release shortly, I'd be happy with releasing 1.4 quickly :) -Mike On 25-Aug-08, at 7: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? On Mon, Aug 25, 2008 at 7:51 PM, Otis Gospodnetic < [EMAIL PROTECTED]> wrote: +1 for Lucene upgrade +1 for a release (I *think* none of the recent SOLR-7** issues have to go in 1.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: 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 -- Regards, Shalin Shekhar Mangar.
Re: 1.3 status
: 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 it more complicated for people to merge bug fixes from the trunk to the release branch (or viceversa) 2) it creates noise that can distract/confuse people about what has been committed where 3) ideally people should be focused on improving documentation and fixing build for the impeding release, not getting too far ahead of ourselves with the next release. if people really want to work on future features that's fine, but we tend to work mainly with patches anyway -- waiting a few days to commit a new feature patch to the trunk isn't that big of a deal. -Hoss
Re: 1.3 status
: 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 bunch of cool Correct. If a 1.3.1 release exists it should be 1.3 with bug fixes - no new features. There's nothing to stop a 1.4 release with new features from coming out a week after 1.3 if people think it's warranted. -Hoss
Re: 1.3 status
: 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 improvements on the trunk for 7-10 days, 3) create a 1.3 release branch at some point ~Sep3-6 4) start reviewing/voting on release candidates at the point where #1 adn #2 corrispond to the "Code Freeze" and #3 and #4 corrispond to "Making a release" of this wiki page... http://wiki.apache.org/solr/HowToRelease ..correct? -Hoss
Re: 1.3 status
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 the the upcoming Lucene 2.4? Jan-Pascal signature.asc Description: OpenPGP digital signature
Re: 1.3 status
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* on the 27th 2) focus on bug fixes and documentation improvements on the trunk for 7-10 days, 3) create a 1.3 release branch at some point ~Sep3-6 4) start reviewing/voting on release candidates at the point where #1 adn #2 corrispond to the "Code Freeze" and #3 and #4 corrispond to "Making a release" of this wiki page... http://wiki.apache.org/solr/HowToRelease I think in Lucene, we usually branch on freeze, too, and then apply patches to both, if need be, this way trunk can move forward.
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
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 the 2.4 issues outstanding [1], none strike me as
particularly troublesome to Solr, so being on something close to 2.4
seems OK to me. As Otis said, LUCENE-1333 would be nice to have.
Thus, I am leaning towards going ahead w/ Solr release in the very
near future (looks like we have 4 outstanding issues [2]) w/ a Lucene
that is as close to trunk/2.4 as we feel possible.
-Grant
[1] Lucene Issues
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310110&fixfor=12312681
[2] Solr Issues
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310230&fixfor=12312486
On Aug 19, 2008, at 9:25 AM, Mark Miller wrote:
Now that Lucene 1.4 looks underway, there seems to be a bit of a
dilemma. Solr 1.3 release seems to be planned a bit ahead of Lucene
1.4. Release just before a Lucene release, or wait and get a nice
even Lucene 1.4 release?
Even if there is a wait for 1.4, if the past is any clue, solr 1.3
will quickly be outdated with 1.4.1 anyway.
- Mark
Lars Kotthoff (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623522
#action_12623522 ]
Lars Kotthoff commented on SOLR-697:
Can we update the jars rather sooner than later (i.e. now) so that
people get a chance to test everything before the 1.3 release?
Update Lucene jar before 1.3 release (was: Lucene
TimeLimitCollector)
-
Key: SOLR-697
URL: https://issues.apache.org/jira/browse/SOLR-697
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 1.3
Reporter: Wayne Graham
Fix For: 1.3
When instantiating a SolrCore using the Solr API, a Lucene
exception is thrown
{{
org.apache.solr.core.SolrResourceLoader createClassLoader
INFO: Reusing parent classloader
Exception in thread "main" java.lang.NoClassDefFoundError: org/
apache/lucene/search/TimeLimitedCollector$TimeExceededException
at org.apache.solr.core.SolrConfig.(SolrConfig.java:
132)
at org.apache.solr.core.SolrConfig.(SolrConfig.java:
101)
...
}}
Updating the lucene-core-2.4-dev.jar that is included in the
nightly to a more current snapshot resolves the problem (tested
with Lucene r685576).
Re: Solr 1.3 Status, Lucene Status was Re: [jira] Commented: (SOLR-697) Update Lucene jar before 1.3 release
I very much agree!
I even feel that SOLR-646 could go in as-is (basing this on Ryan's useful
summary of that issue's latest status) today.
Grant, any chance you can do a release this Friday or next Monday?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- 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'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 the 2.4 issues outstanding [1], none strike me as
> particularly troublesome to Solr, so being on something close to 2.4
> seems OK to me. As Otis said, LUCENE-1333 would be nice to have.
>
> Thus, I am leaning towards going ahead w/ Solr release in the very
> near future (looks like we have 4 outstanding issues [2]) w/ a Lucene
> that is as close to trunk/2.4 as we feel possible.
>
> -Grant
>
> [1] Lucene Issues
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310110&fixfor=12312681
>
> [2] Solr Issues
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310230&fixfor=12312486
>
>
> On Aug 19, 2008, at 9:25 AM, Mark Miller wrote:
>
> > Now that Lucene 1.4 looks underway, there seems to be a bit of a
> > dilemma. Solr 1.3 release seems to be planned a bit ahead of Lucene
> > 1.4. Release just before a Lucene release, or wait and get a nice
> > even Lucene 1.4 release?
> >
> > Even if there is a wait for 1.4, if the past is any clue, solr 1.3
> > will quickly be outdated with 1.4.1 anyway.
> >
> > - Mark
> >
> >
> > Lars Kotthoff (JIRA) wrote:
> >>[
> https://issues.apache.org/jira/browse/SOLR-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623522
>
>
> >> #action_12623522 ]
> >> Lars Kotthoff commented on SOLR-697:
> >>
> >>
> >> Can we update the jars rather sooner than later (i.e. now) so that
> >> people get a chance to test everything before the 1.3 release?
> >>
> >>
> >>> Update Lucene jar before 1.3 release (was: Lucene
> >>> TimeLimitCollector)
> >>> -
> >>>
> >>>Key: SOLR-697
> >>>URL: https://issues.apache.org/jira/browse/SOLR-697
> >>>Project: Solr
> >>> Issue Type: Bug
> >>> Components: update
> >>> Affects Versions: 1.3
> >>> Reporter: Wayne Graham
> >>>Fix For: 1.3
> >>>
> >>>
> >>> When instantiating a SolrCore using the Solr API, a Lucene
> >>> exception is thrown
> >>> {{
> >>> org.apache.solr.core.SolrResourceLoader createClassLoader
> >>> INFO: Reusing parent classloader
> >>> Exception in thread "main" java.lang.NoClassDefFoundError: org/
> >>> apache/lucene/search/TimeLimitedCollector$TimeExceededException
> >>>at org.apache.solr.core.SolrConfig.(SolrConfig.java:
> >>> 132)
> >>>at org.apache.solr.core.SolrConfig.(SolrConfig.java:
> >>> 101)
> >>> ...
> >>> }}
> >>> Updating the lucene-core-2.4-dev.jar that is included in the
> >>> nightly to a more current snapshot resolves the problem (tested
> >>> with Lucene r685576).
> >>>
> >>
> >>
> >
Re: Solr 1.3 Status, Lucene Status was Re: [jira] Commented: (SOLR-697) Update Lucene jar before 1.3 release
Next week looks doable. We're pretty close, it seems, if we can
resist the urge to add more issues in :-)
-Grant
On Aug 20, 2008, at 1:31 AM, Otis Gospodnetic wrote:
I very much agree!
I even feel that SOLR-646 could go in as-is (basing this on Ryan's
useful summary of that issue's latest status) today.
Grant, any chance you can do a release this Friday or next Monday?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- 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'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 the 2.4 issues outstanding [1], none strike me as
particularly troublesome to Solr, so being on something close to 2.4
seems OK to me. As Otis said, LUCENE-1333 would be nice to have.
Thus, I am leaning towards going ahead w/ Solr release in the very
near future (looks like we have 4 outstanding issues [2]) w/ a Lucene
that is as close to trunk/2.4 as we feel possible.
-Grant
[1] Lucene Issues
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310110&fixfor=12312681
[2] Solr Issues
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310230&fixfor=12312486
On Aug 19, 2008, at 9:25 AM, Mark Miller wrote:
Now that Lucene 1.4 looks underway, there seems to be a bit of a
dilemma. Solr 1.3 release seems to be planned a bit ahead of Lucene
1.4. Release just before a Lucene release, or wait and get a nice
even Lucene 1.4 release?
Even if there is a wait for 1.4, if the past is any clue, solr 1.3
will quickly be outdated with 1.4.1 anyway.
- Mark
Lars Kotthoff (JIRA) wrote:
[
https://issues.apache.org/jira/browse/SOLR-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623522
#action_12623522 ]
Lars Kotthoff commented on SOLR-697:
Can we update the jars rather sooner than later (i.e. now) so that
people get a chance to test everything before the 1.3 release?
Update Lucene jar before 1.3 release (was: Lucene
TimeLimitCollector)
-
Key: SOLR-697
URL: https://issues.apache.org/jira/browse/SOLR-697
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 1.3
Reporter: Wayne Graham
Fix For: 1.3
When instantiating a SolrCore using the Solr API, a Lucene
exception is thrown
{{
org.apache.solr.core.SolrResourceLoader createClassLoader
INFO: Reusing parent classloader
Exception in thread "main" java.lang.NoClassDefFoundError: org/
apache/lucene/search/TimeLimitedCollector$TimeExceededException
at org.apache.solr.core.SolrConfig.(SolrConfig.java:
132)
at org.apache.solr.core.SolrConfig.(SolrConfig.java:
101)
...
}}
Updating the lucene-core-2.4-dev.jar that is included in the
nightly to a more current snapshot resolves the problem (tested
with Lucene r685576).
--
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
