I want to include SOLR-13834 in 8.3. If someone can please review, would be nice. If someone wants me to hold it off, I'm okay doing so. Thanks, Ishan
On Fri, 11 Oct, 2019, 9:05 PM Yonik Seeley, <[email protected]> wrote: > I've fixed the live-split data loss bug found earlier in > https://issues.apache.org/jira/browse/SOLR-13815 > and I think it should go into 8.3 as well. > -Yonik > > > On Fri, Oct 11, 2019 at 11:08 AM Ishan Chattopadhyaya < > [email protected]> wrote: > >> Sure, sounds good Andrzej, Gus and Joel. Thanks! >> >> On Fri, Oct 11, 2019 at 4:09 AM Joel Bernstein <[email protected]> >> wrote: >> > >> > I've plan on merging this bug fix as well: >> https://issues.apache.org/jira/browse/SOLR-13829 >> > >> > Joel Bernstein >> > http://joelsolr.blogspot.com/ >> > >> > >> > On Thu, Oct 10, 2019 at 6:21 PM Gus Heck <[email protected]> wrote: >> >> >> >> I'll be merging SOLR-13760 tonight as well >> >> >> >> >> >> On Thu, Oct 10, 2019 at 5:57 PM Andrzej Białecki <[email protected]> >> wrote: >> >>> >> >>> Hi Ishan, >> >>> >> >>> Me too, me too :) I’d like to merge a bug fix for SOLR-13828. >> >>> >> >>> On 9 Oct 2019, at 15:38, Ishan Chattopadhyaya < >> [email protected]> wrote: >> >>> >> >>> +1, Dat! Please go ahead. >> >>> >> >>> On Wed, 9 Oct, 2019, 2:33 PM Andrzej Białecki, <[email protected]> wrote: >> >>>> >> >>>> It’s marked as Minor in Jira, but after reading the description it >> sounds scary - IMHO it should be at least well investigated before 8.3 in >> order to determine whether it causes real damage (apart from looking scary >> and filling the logs). >> >>>> >> >>>> +1 from me. >> >>>> >> >>>> On 9 Oct 2019, at 10:48, Đạt Cao Mạnh <[email protected]> >> wrote: >> >>>> >> >>>> Hi Ishan, guys >> >>>> >> >>>> I want to include the fix for >> https://issues.apache.org/jira/browse/SOLR-13293 in this release. Hoping >> that is ok! >> >>>> >> >>>> Thanks! >> >>>> >> >>>> On Tue, Oct 8, 2019 at 4:02 PM Uwe Schindler <[email protected]> >> wrote: >> >>>>> >> >>>>> ASF Jenkins Jobs also reconfigured. >> >>>>> >> >>>>> I left the 8.2 Refguide job in the queue (I cloned it), not sure if >> that one is still needed. All other jobs are 8.3 now. >> >>>>> >> >>>>> Uwe >> >>>>> >> >>>>> ----- >> >>>>> Uwe Schindler >> >>>>> Achterdiek 19, D-28357 Bremen >> >>>>> https://www.thetaphi.de >> >>>>> eMail: [email protected] >> >>>>> >> >>>>> > -----Original Message----- >> >>>>> > From: Uwe Schindler <[email protected]> >> >>>>> > Sent: Tuesday, October 8, 2019 4:49 PM >> >>>>> > To: [email protected] >> >>>>> > Subject: RE: 8.3 release >> >>>>> > >> >>>>> > Policeman Jenkins builds and tests 8.3 for Windows and Linux. >> >>>>> > >> >>>>> > Uwe >> >>>>> > >> >>>>> > ----- >> >>>>> > Uwe Schindler >> >>>>> > Achterdiek 19, D-28357 Bremen >> >>>>> > https://www.thetaphi.de >> >>>>> > eMail: [email protected] >> >>>>> > >> >>>>> > > -----Original Message----- >> >>>>> > > From: Ishan Chattopadhyaya <[email protected]> >> >>>>> > > Sent: Tuesday, October 8, 2019 4:32 PM >> >>>>> > > To: Lucene Dev <[email protected]>; Uwe Schindler >> >>>>> > > <[email protected]>; Steve Rowe <[email protected]> >> >>>>> > > Subject: Re: 8.3 release >> >>>>> > > >> >>>>> > > I've cut the 8.3 branch. Please feel free to push in any bug >> fix. For >> >>>>> > > any feature, please let me know to see how we can accommodate it >> >>>>> > > safely. >> >>>>> > > I'm planning to get myself familiarized with what I need to do >> for the >> >>>>> > > ref guide release (simultaneously with the binary release). So, >> most >> >>>>> > > likely, I'll be able to build artifacts in another week's time. >> >>>>> > > @Uwe Schindler / @Steve Rowe would it be possible to please >> create a >> >>>>> > > Jenkins branch for 8.3? >> >>>>> > > Thanks, >> >>>>> > > Ishan >> >>>>> > > >> >>>>> > > On Mon, Oct 7, 2019 at 4:17 PM Ishan Chattopadhyaya >> >>>>> > > <[email protected]> wrote: >> >>>>> > > > >> >>>>> > > > I'll cut the branch in 12-24 hours from now. If someone has >> anything >> >>>>> > > > to put into branch_8x now, please feel free. >> >>>>> > > > If someone has a non-bugfix issue that they want to push in >> to 8.3 >> >>>>> > > > after the branch cut, but you're sure it will not disrupt the >> >>>>> > > > stability of the release, please let me know and we can >> discuss on a >> >>>>> > > > case-by-case basis. >> >>>>> > > > >> >>>>> > > > On Wed, Oct 2, 2019 at 8:50 PM Mikhail Khludnev < >> [email protected]> >> >>>>> > > wrote: >> >>>>> > > > > >> >>>>> > > > > Excuse me. I have to recall this message regarding >> SOLR-13764. >> >>>>> > > > > >> >>>>> > > > > On Mon, Sep 30, 2019 at 10:56 PM Mikhail Khludnev >> >>>>> > > <[email protected]> wrote: >> >>>>> > > > >> >> >>>>> > > > >> Ishan, thanks for update. >> >>>>> > > > >> May I propose to hold it for this week, beside of the >> severe issues you >> >>>>> > > mentioned, I'd like to drop pretty neat JSON Query parser for >> Interval >> >>>>> > > Queries https://issues.apache.org/jira/browse/SOLR-13764 this >> week. >> >>>>> > > > >> >> >>>>> > > > >> пн, 30 сент. 2019 г., 18:04 Ishan Chattopadhyaya >> >>>>> > > <[email protected]>: >> >>>>> > > > >>> >> >>>>> > > > >>> * Due to some unfinished and half merged work in >> SOLR-13661, we >> >>>>> > are >> >>>>> > > in >> >>>>> > > > >>> a difficult position for a branch cutting today (as I had >> proposed). >> >>>>> > > > >>> I have documented the options on how to deal with that >> immediately >> >>>>> > > in >> >>>>> > > > >>> that issue. I'll work to resolve the situation and cut a >> branch as >> >>>>> > > > >>> soon as possible. >> >>>>> > > > >>> * SOLR-13677 is also a blocker for release, but I can >> proceed with the >> >>>>> > > > >>> branch cutting. >> >>>>> > > > >>> >> >>>>> > > > >>> I'll take a look at the ref guide's simultaneous release >> as we reach >> >>>>> > > > >>> closer to building the artifacts. >> >>>>> > > > >>> Thanks, >> >>>>> > > > >>> Ishan >> >>>>> > > > >>> >> >>>>> > > > >>> On Wed, Sep 18, 2019 at 9:06 PM Cassandra Targett >> >>>>> > > <[email protected]> wrote: >> >>>>> > > > >>> > >> >>>>> > > > >>> > As I’ve mentioned to some of you over the past couple >> of weeks, I >> >>>>> > > want to propose that we don’t “release” the Ref Guide at all >> the way we >> >>>>> > have >> >>>>> > > been doing it. >> >>>>> > > > >>> > >> >>>>> > > > >>> > It deserves a separate thread, which since it’s come up >> a few times >> >>>>> > > this week I should start now, but in essence, my idea is to no >> longer treat >> >>>>> > the >> >>>>> > > PDF as a release artifact that requires a vote, and publish the >> HTML as our >> >>>>> > > primary version of the Ref Guide in effectively the same way we >> publish the >> >>>>> > > javadocs (at the same time as the binary artifacts). >> >>>>> > > > >>> > >> >>>>> > > > >>> > Instead of highjacking this thread with that discussion >> since it has >> >>>>> > > several aspects, let me send another mail on it where I can >> flesh it out >> >>>>> > more >> >>>>> > > and we can discuss there. I have the mail mostly queued up and >> ready to >> >>>>> > go >> >>>>> > > already. >> >>>>> > > > >>> > >> >>>>> > > > >>> > Cassandra >> >>>>> > > > >>> > On Sep 18, 2019, 10:23 AM -0500, Gus Heck >> >>>>> > <[email protected]>, >> >>>>> > > wrote: >> >>>>> > > > >>> > >> >>>>> > > > >>> > I learned recently that it's actually all documented >> here: >> >>>>> > > >> https://lucene.apache.org/solr/guide/8_1/how-to-contribute.html#ref- >> >>>>> > > guide-publication-process >> >>>>> > > > >>> > >> >>>>> > > > >>> > On Tue, Sep 17, 2019 at 7:31 PM Ishan Chattopadhyaya >> >>>>> > > <[email protected]> wrote: >> >>>>> > > > >>> >> >> >>>>> > > > >>> >> Hi Adrien, >> >>>>> > > > >>> >> Indeed, meant to write about starting a vote. >> >>>>> > > > >>> >> >> >>>>> > > > >>> >> @Gus, I'll have to let Cassandra weigh in on this one >> as I'm not >> >>>>> > very >> >>>>> > > familiar with the ref guide release process. >> >>>>> > > > >>> >> >> >>>>> > > > >>> >> Regards, >> >>>>> > > > >>> >> Ishan >> >>>>> > > > >>> >> >> >>>>> > > > >>> >> On Mon, 16 Sep, 2019, 7:28 PM Adrien Grand, >> >>>>> > > <[email protected]> wrote: >> >>>>> > > > >>> >>> >> >>>>> > > > >>> >>> +1 to start working on 8.3 >> >>>>> > > > >>> >>> >> >>>>> > > > >>> >>> Did you mean "start a vote" when you wrote "release >> the >> >>>>> > > artifacts"? It >> >>>>> > > > >>> >>> got me wondering because I don't think we frequently >> managed >> >>>>> > to >> >>>>> > > go >> >>>>> > > > >>> >>> from cutting a branch to releasing artifacts in so >> little time in the >> >>>>> > > > >>> >>> past. >> >>>>> > > > >>> >>> >> >>>>> > > > >>> >>> On Mon, Sep 16, 2019 at 5:52 PM Ishan Chattopadhyaya >> >>>>> > > > >>> >>> <[email protected]> wrote: >> >>>>> > > > >>> >>> > >> >>>>> > > > >>> >>> > Hi all, >> >>>>> > > > >>> >>> > We have a lot of unreleased features and fixes. I >> propose that >> >>>>> > we >> >>>>> > > cut >> >>>>> > > > >>> >>> > a 8.3 branch in two weeks (in order to have >> sufficient time to >> >>>>> > > bake in >> >>>>> > > > >>> >>> > all in-progress features). If there are no >> objections to doing so, I >> >>>>> > > > >>> >>> > can volunteer for the release as an RM and plan for >> cutting a >> >>>>> > > release >> >>>>> > > > >>> >>> > branch on 30 September (and release the artifacts >> about 3-4 >> >>>>> > days >> >>>>> > > after >> >>>>> > > > >>> >>> > that). >> >>>>> > > > >>> >>> > >> >>>>> > > > >>> >>> > WDYT? >> >>>>> > > > >>> >>> > Regards, >> >>>>> > > > >>> >>> > Ishan >> >>>>> > > > >>> >>> > >> >>>>> > > > >>> >>> > >> --------------------------------------------------------------------- >> >>>>> > > > >>> >>> > To unsubscribe, e-mail: >> [email protected] >> >>>>> > > > >>> >>> > For additional commands, e-mail: >> [email protected] >> >>>>> > > > >>> >>> > >> >>>>> > > > >>> >>> >> >>>>> > > > >>> >>> >> >>>>> > > > >>> >>> -- >> >>>>> > > > >>> >>> Adrien >> >>>>> > > > >>> >>> >> >>>>> > > > >>> >>> >> --------------------------------------------------------------------- >> >>>>> > > > >>> >>> To unsubscribe, e-mail: >> [email protected] >> >>>>> > > > >>> >>> For additional commands, e-mail: >> [email protected] >> >>>>> > > > >>> >>> >> >>>>> > > > >>> > >> >>>>> > > > >>> > >> >>>>> > > > >>> > -- >> >>>>> > > > >>> > http://www.needhamsoftware.com (work) >> >>>>> > > > >>> > http://www.the111shift.com (play) >> >>>>> > > > >>> >> >>>>> > > > >>> >> --------------------------------------------------------------------- >> >>>>> > > > >>> To unsubscribe, e-mail: [email protected] >> >>>>> > > > >>> For additional commands, e-mail: >> [email protected] >> >>>>> > > > >>> >> >>>>> > > > > >> >>>>> > > > > >> >>>>> > > > > -- >> >>>>> > > > > Sincerely yours >> >>>>> > > > > Mikhail Khludnev >> >>>>> > > >> >>>>> > > >> --------------------------------------------------------------------- >> >>>>> > > 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] >> >>>>> >> >>>> >> >>>> >> >>>> -- >> >>>> Best regards, >> >>>> Cao Mạnh Đạt >> >>>> E-mail: [email protected] >> >>>> >> >>>> >> >>> >> >> >> >> >> >> -- >> >> http://www.needhamsoftware.com (work) >> >> http://www.the111shift.com (play) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
