Releases don't come for free. That is a nasty bug. My 2 cents would be to
relax for a day or two and see what comes of a fix for that issue. It
shouldn't hold things up a long time, but not holding things up for a short
bit seems counter productive to me. The idea that anyone legitimate is
slapping in releases as fast as they come out in a production env is hard
for me to buy. Apache really should move on the fastest unit of time of a
couple days in most cases.

I like that over the years we have become a lot more pro, you can't stop
the release train baby, at best you can pause it 5 seconds. But now that we
have enabled the train to run everyone over, might be worth stepping it
back just half a step.

- Mark

On Wed, Apr 12, 2017 at 11:15 AM Joel Bernstein <[email protected]> wrote:

> Here are the release notes for bug fixes that are ready to ship:
>
> https://wiki.apache.org/lucene-java/ReleaseNote651
> https://wiki.apache.org/solr/ReleaseNote651
>
> There are Solr bug fixes that affect non-Solr Cloud systems, and Lucene
> bugs. So there will be plenty of users who can benefit from a 6.5.1
> release.
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 12, 2017 at 10:58 AM, Cassandra Targett <[email protected]
> > wrote:
>
> No, Joel initially proposed 6.5.1 to fix SOLR-10341 (back on 30 Mar).
> SOLR-10420 was reported after he'd already announced his intention to
> RM a 6.5.1.
>
> On Wed, Apr 12, 2017 at 9:54 AM, Walter Underwood <[email protected]>
> wrote:
> > SOLR-10420 is the only reason I would install a 6.5.1. That is a serious
> bug
> > that affects every user of Solr Cloud.
> >
> > That bug was the reason why the 6.5.1 process was started, right?
> >
> > wunder
> > Walter Underwood
> > [email protected]
> > http://observer.wunderwood.org/  (my blog)
> >
> >
> > On Apr 12, 2017, at 7:14 AM, Joel Bernstein <[email protected]> wrote:
> >
> > We have a couple options here:
> >
> > 1) The vote ends for this release tomorrow. We can continue with this
> > release and ship 6.5.1. In the background start working on 6.5.2.
> >
> > 2) Or we could respin 6.5.1 to include SOLR-10420. The problem with this
> is
> > it restarts the clock on the 6.5.1 and delays other bug fixes.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 12, 2017 at 9:48 AM, Đạt Cao Mạnh <[email protected]>
> > wrote:
> >>
> >> Sorry Joel, but can we wait for SOLR-10420, this is a serious bug that
> >> leaking one SolrZkClient per second on the Overseer node.
> >>
> >> On Tue, Apr 11, 2017 at 6:34 PM Tommaso Teofili
> >> <[email protected]> wrote:
> >>>
> >>> +1
> >>>
> >>> SUCCESS! [2:25:09.313218]
> >>>
> >>> Tommaso
> >>>
> >>> Il giorno mar 11 apr 2017 alle ore 06:47 Shalin Shekhar Mangar
> >>> <[email protected]> ha scritto:
> >>>>
> >>>> +1
> >>>>
> >>>> SUCCESS! [2:03:24.673867]
> >>>>
> >>>> On Mon, Apr 10, 2017 at 8:31 AM, Joel Bernstein <[email protected]>
> >>>> wrote:
> >>>> > Please vote for release candidate 1 for Lucene/Solr 6.5.1
> >>>> >
> >>>> > The artifacts can be downloaded from:
> >>>> >
> >>>> >
> >>>> >
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC1-revf88f850034eee845b8021af47ecffc9c42aa8539
> >>>> >
> >>>> > You can run the smoke tester directly with this command:
> >>>> >
> >>>> > python3 -u dev-tools/scripts/smokeTestRelease.py \
> >>>> >
> >>>> >
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC1-revf88f850034eee845b8021af47ecffc9c42aa8539
> >>>> >
> >>>> > Here's my +1
> >>>> >
> >>>> > SUCCESS! [0:40:54.049621]
> >>>> >
> >>>> > Joel Bernstein
> >>>> > http://joelsolr.blogspot.com/
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Regards,
> >>>> Shalin Shekhar Mangar.
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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]
>
>
> --
- Mark
about.me/markrmiller

Reply via email to