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
