+1, thanks Jan! :-)

On Fri, May 3, 2019 at 3:08 AM Jan Høydahl <jan....@cominvent.com> wrote:
>
> I have a fix for https://issues.apache.org/jira/browse/SOLR-12120 that I'll 
> commit also to 8_1 since it fixes a real bug that has caused test failures 
> 20% of the time. Thus it will stabilize the tests.
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> 2. mai 2019 kl. 21:36 skrev Ishan Chattopadhyaya <ichattopadhy...@gmail.com>:
>
> Due to failing tests (esp. PeerSyncTest and TestInPlaceUpdatesDistrib,
> among others), I'm postponing the RC (which I was supposed to spin
> today).
> Assuming we know the cause of these failures (SOLR-12833?) and we can
> fix it soon enough, I'll spin up the RC1 around 48-72 hours from now.
> Let me know if there are any objections.
>
> If there are any bugfixes whose inclusion into 8.1 would be nice (and
> doesn't impact the stability of the release or tests), please feel
> free to commit to the 8.1 branch.
> Thanks,
> Ishan
>
> On Fri, May 3, 2019 at 1:02 AM Ishan Chattopadhyaya
> <ichattopadhy...@gmail.com> wrote:
>
>
> +1, David.
>
> On Wed, May 1, 2019 at 7:07 PM David Smiley <david.w.smi...@gmail.com> wrote:
>
>
> FYI today in some hours I plan to commit a solr-ref-guide documentation 
> update to 8.1 -- https://github.com/apache/lucene-solr/pull/647 so that an 
> 8.1 feature is properly documented RE nested docs and partial/atomic updates.
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley
>
>
> On Wed, May 1, 2019 at 7:19 AM Uwe Schindler <u...@thetaphi.de> wrote:
>
>
> I can help out later!
>
> Uwe
>
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> -----Original Message-----
> From: Ishan Chattopadhyaya <ichattopadhy...@gmail.com>
> Sent: Wednesday, May 1, 2019 11:54 AM
> To: Lucene Dev <dev@lucene.apache.org>
> Subject: Re: Lucene/Solr 8.1
>
> I've cut the release branch, branch_8_1.
> Seems like I don't have authorization to create a new Jenkins job for
> 8.1. Can someone with the access please help?
>
> On Tue, Apr 30, 2019 at 9:48 PM Ishan Chattopadhyaya
> <ichattopadhy...@gmail.com> wrote:
>
>
> Hi all,
> I'll cut the release branch in around 12-18 hours.
> Planning to build the first RC on 2nd May.
> Thanks and regards,
> Ishan
>
> On Fri, Apr 19, 2019 at 12:04 AM Joel Bernstein <joels...@gmail.com>
>
> wrote:
>
>
> +1 to April 30th timeframe.
>
> On Thu, Apr 18, 2019 at 12:40 PM Erick Erickson
>
> <erickerick...@gmail.com> wrote:
>
>
> 30 Apr seems reasonable to me for cutting the branch.
>
> Thanks!
>
> On Apr 18, 2019, at 9:23 AM, Ishan Chattopadhyaya
>
> <ichattopadhy...@gmail.com> wrote:
>
>
> I'm expecting
> you'd build a RC soon after cutting the branch?
>
>
> Sure, maybe a day or two after the branch cutting.
>
>
> On Wed, Apr 17, 2019 at 8:51 PM Adrien Grand <jpou...@gmail.com>
>
> wrote:
>
>
> +1 to do a 8.1 soon too, thanks Ishan for volunteering! I'm expecting
> you'd build a RC soon after cutting the branch?
>
> On Wed, Apr 17, 2019 at 10:08 AM Ishan Chattopadhyaya
> <ichattopadhy...@gmail.com> wrote:
>
>
> +1 for a 8.1 soon. I can volunteer for RM.
> Does 30 April (about 2 weeks from now) sound reasonable for a
>
> branch cutting?
>
>
> On Wed, Apr 17, 2019 at 1:14 PM Ignacio Vera
>
> <iver...@gmail.com> wrote:
>
>
> Hi all,
>
> Feature freeze for 8.0 was long time ago (January 29th) and there
>
> is interesting stuff that has not been released yet. In Lucene in particular
> there is the new BKD tree strategy for segment merging  which provides a
> significant performance boost for high dimensions, the new Luke module or
> the new query visitor API for naming a few. I see that in Solr there is as 
> well
> quite a few unreleased changes.
>
>
> I might not be able to be the release manager this time as I will be
>
> on holidays the next few weeks but I would like to gauge the interest in the
> community to have a new release soonish.
>
>
> Cheers,
>
> Ignacio
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
>
> --
> Adrien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to