red to do the docker 8.6.1 release already:
> https://github.com/docker-solr/docker-solr/issues/328#issuecomment-666494362
>
> I recommend other committers interested in docker "Watch" that repo, just
> as you probably do for lucene-solr.
>
> ~ David Smiley
> Apache L
FYI I volunteered to do the docker 8.6.1 release already:
https://github.com/docker-solr/docker-solr/issues/328#issuecomment-666494362
I recommend other committers interested in docker "Watch" that repo, just
as you probably do for lucene-solr.
~ David Smiley
Apache Lucene/Solr Search
ichattopadhy...@gmail.com> wrote:
>
>> For some reason, 8.6.0 docker images are not generated and pushed. After
>> the 8.6.1 release, can we ensure that the docker images are pushed? Any
>> idea how does that happen, generally?
>> Can we add this as a step in the releas
ter
> the 8.6.1 release, can we ensure that the docker images are pushed? Any
> idea how does that happen, generally?
> Can we add this as a step in the release process please?
>
> On Fri, Jul 31, 2020 at 2:47 AM Houston Putman
> wrote:
>
>> The first RC has been pushed
For some reason, 8.6.0 docker images are not generated and pushed. After
the 8.6.1 release, can we ensure that the docker images are pushed? Any
idea how does that happen, generally?
Can we add this as a step in the release process please?
On Fri, Jul 31, 2020 at 2:47 AM Houston Putman
wrote
, 2020 at 11:51 AM Houston Putman
wrote:
> Ok, I'm finalizing the 8.6.1 release, so please do not push any commits
> unless there is a large bug we have not yet identified.
>
> I'll be sending out the RC1 later today.
>
> - Houston
>
> On Thu, Jul 30, 2020 at 11:
Ok, I'm finalizing the 8.6.1 release, so please do not push any commits
unless there is a large bug we have not yet identified.
I'll be sending out the RC1 later today.
- Houston
On Thu, Jul 30, 2020 at 11:41 AM Atri Sharma wrote:
> This seems like a patch release for targeting a speci
>>>>>>>>>>>
>> >>>>>>>>>>>>>> Then I'll start the release process for 8.6.1.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Please speak up if there is a
t; >>>>>>>>>>>>>> going to push my branch_8_6 that has the offending commits
>> >>>>>>>>>>>>>> reverted and some additional documentation on reverting the
>> >>>>>>>>>>>>
Wed, Jul 22, 2020 at 4:40 PM Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Absolutely, Ilan! Good idea. I initially he
gt;>>> - Houston
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Jul 22, 2020 at 4:40 PM Ishan Chattopadhyaya
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>
Wed, Jul 22, 2020 at 4:40 PM Ishan Chattopadhyaya <
>>>>>>>>>>>>> ichattopadhy...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Absolutely, Ilan! Good idea. I initially hesitated in doing
>&g
hem of the
>>>>>>>>>>>>> issue
>>>>>>>>>>>>> right away anyway.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, 22 Jul, 2020, 11:42 pm Ilan
right away anyway.
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, 22 Jul, 2020, 11:42 pm Ilan Ginzburg, <
>>>>>>>>>>>> ilans...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>&g
to
>> >> > 8.6.1 get the earlier default policy?
>> >> >
>> >> > On Wed, Jul 22, 2020 at 9:09 PM Houston Putman > >> > <mailto:houstonput...@gmail.com>> wrote:
>> >> > >
>> >> > > +1
>> &g
we add a note right away to 8.6 notifying of the
>>>>>>>>>>>> issue?
>>>>>>>>>>>>
>>>>>>>>>>>> Le mer. 22 juil. 2020 à 20:08, Atri Sharma a
>>>>>>>>>>>> écrit :
&g
t;>>>>> On Wed, Jul 22, 2020 at 10:51 PM Houston Putman <
>>>>>>>>>>>> houstonput...@gmail.com> wrote:
>>>>>>>>>>>> >
>>>>>>>>>>>> > If we agree that this warrants a patch re
;>>>>>>>>> > I do think a patch release is reasonable even if users have to
>>>>>>>>>>> take an action when upgrading from 8.6.0. I imagine most users
>>>>>>>>>>> ha
;>>>>>>> > I do think a patch release is reasonable even if users have to
>>>>>>>>>> take an action when upgrading from 8.6.0. I imagine most users
>>>>>>>>>> haven't
>>>>>>>>>> upgraded to 8.6.0 yet, so if we make the pat
his patch added a default
> >> > > autoscaling policy, if users upgrade to 8.6 and then 8.6.1, does the
> >> > > default autoscaling policy stay once they have upgraded? If so we
> >> > > probably want to include instructions in the release notes on how to
> &g
;>>>>>>> easier
>>>>>>>>> for everyone that upgrades between now and when 8.7 is released.
>>>>>>>>> >
>>>>>>>>> > On Wed, Jul 22, 2020 at 12:50 PM Atri Sharma
>>>>>>>>&g
gt;>>> wrote:
>>>>>>>> >>
>>>>>>>> >> Ignore this, I misread your email.
>>>>>>>> >>
>>>>>>>> >> On Wed, Jul 22, 2020 at 9:11 PM Atri Sharma
>>>>>&g
Sharma
>>>>>>> wrote:
>>>>>>> >> >
>>>>>>> >> > Should we not revert the change so that users upgrading from
>>>>>>> 8.6 to
>>>>>>> >> > 8.6.1 get the earlier default
gt;>>>> >> > 8.6.1 get the earlier default policy?
>>>>>> >> >
>>>>>> >> > On Wed, Jul 22, 2020 at 9:09 PM Houston Putman <
>>>>>> houstonput...@gmail.com> wrote:
>>>>>> >>
20 at 9:09 PM Houston Putman <
>>>>> houstonput...@gmail.com> wrote:
>>>>> >> > >
>>>>> >> > > +1
>>>>> >> > >
>>>>> >> > > Question about the change. Since this patch added a d
Putman <
>>>>> houstonput...@gmail.com> wrote:
>>>>> >> > >
>>>>> >> > > +1
>>>>> >> > >
>>>>> >> > > Question about the change. Since this patch added a default
>>>&g
t;>> houstonput...@gmail.com> wrote:
>>>> >> > >
>>>> >> > > +1
>>>> >> > >
>>>> >> > > Question about the change. Since this patch added a default
>>>> autoscaling policy, if users upgrade to 8.6
scaling policy, if users upgrade to 8.6 and then 8.6.1, does the
>>> default autoscaling policy stay once they have upgraded? If so we probably
>>> want to include instructions in the release notes on how to fix this issue
>>> once upgrading.
>>> >> > >
>
1, does the
>> default autoscaling policy stay once they have upgraded? If so we probably
>> want to include instructions in the release notes on how to fix this issue
>> once upgrading.
>> >> > >
>> >> > > - Houston
>> >> > >
>> >>
structions in the release notes on how to fix this issue
> once upgrading.
> >> > >
> >> > > - Houston
> >> > >
> >> > > On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
> >> > >>
> &
graded? If so we probably want
>> > > to include instructions in the release notes on how to fix this issue
>> > > once upgrading.
>> > >
>> > > - Houston
>> > >
>> > > On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyay
t; > > On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyaya <
>> ichattopadhy...@gmail.com> wrote:
>> > >>
>> > >> Hi,
>> > >> There was a performance regression identified in 8.6.0 release due
>> to SOLR-12845. I think it is ser
to include instructions in the release notes on how to fix this issue
>> once upgrading.
>> > >
>> > > - Houston
>> > >
>> > > On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyaya <
>> ichattopadhy...@gmail.com> wrote:
>> &g
2, 2020 at 1:53 AM Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
> > >>
> > >> Hi,
> > >> There was a performance regression identified in 8.6.0 release due to
> SOLR-12845. I think it is serious enough to warrant an immediate bug fix
> relea
e release notes on how to fix this issue once
> > upgrading.
> >
> > - Houston
> >
> > On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyaya
> > wrote:
> >>
> >> Hi,
> >> There was a performance regression identified in 8.6.0 release due t
;
>> ichattopadhy...@gmail.com> wrote:
>>
>>> Hi,
>>> There was a performance regression identified in 8.6.0 release due to
>>> SOLR-12845. I think it is serious enough to warrant an immediate bug fix
>>> release.
>>>
>>> I propos
i,
>> There was a performance regression identified in 8.6.0 release due to
>> SOLR-12845. I think it is serious enough to warrant an immediate bug fix
>> release.
>>
>> I propose a 8.6.1 release. Unfortunately, I'll be unable to volunteer for
>> this releas
>>
>> Hi,
>> There was a performance regression identified in 8.6.0 release due to
>> SOLR-12845. I think it is serious enough to warrant an immediate bug fix
>> release.
>>
>> I propose a 8.6.1 release. Unfortunately, I'll be unable to volunteer fo
+1
On Wed, Jul 22, 2020 at 11:23 AM Ishan Chattopadhyaya
wrote:
>
> Hi,
> There was a performance regression identified in 8.6.0 release due to
> SOLR-12845. I think it is serious enough to warrant an immediate bug fix
> release.
>
> I propose a 8.6.1 release. Unfortun
.
- Houston
On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> Hi,
> There was a performance regression identified in 8.6.0 release due to
> SOLR-12845. I think it is serious enough to warrant an immediate bug fix
> release.
>
> I
Hi,
There was a performance regression identified in 8.6.0 release due to
SOLR-12845. I think it is serious enough to warrant an immediate bug fix
release.
I propose a 8.6.1 release. Unfortunately, I'll be unable to volunteer for
this release owning to some other commitments, however Andrzej
41 matches
Mail list logo
