Figured it out and downgraded to a trivial bug.
-Yonik
On Wed, Aug 12, 2015 at 1:57 PM, Yonik Seeley wrote:
> I've set this as a blocker until we know more about the actual impact.
> https://issues.apache.org/jira/browse/SOLR-7917
>
> -Yonik
>
>
> On Tue, Aug 11, 2015 at 12:49 PM, Noble Paul wro
t;>> ...not sure if marking this "feature" as a "blocker" at that point would
>>> have really been a good process to follow?
>>>
>>> (perhaps a new "Blocker: Bug" should have been created? "Need to fix
>>> permissions A
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14680361
>>
>> ...not sure if marking this "feature" as a "blocker" at that point would
>> have really been a good process to follow?
>>
>> (perhaps a new "Blocker: Bug" should
tcher, Senior Solutions Architect
>> http://www.lucidworks.com
>>
>>
>>
>>
>> On Aug 5, 2015, at 11:09 AM, Noble Paul wrote:
>>
>> I have created the lucene_solr_5_3 branch.
>> If anything new must go into 5.3 release please communicate it here
>&
I've committed a trivial logging/nocommit statement removal (SOLR-7911). I
hope that is ok.
On Mon, Jul 27, 2015 at 1:56 AM, Noble Paul wrote:
> Hi,
> I would like to volunteer myself as the RM for 5.3 release. I plan to
> cut the 5.3 release branch by next
llow?
>
> (perhaps a new "Blocker: Bug" should have been created? "Need to fix
> permissions API syntax before 5.3 release otherwise it's a backcompat
> nightmare" ?)
OK thanks for the summary Hoss, I didn't read the comments on the
issue to see the backstory.
em.issuetabpanels:comment-tabpanel#comment-14680361
...not sure if marking this "feature" as a "blocker" at that point would
have really been a good process to follow?
(perhaps a new "Blocker: Bug" should have been created? "Need to fix
permissions API syntax before
to be sure
>> the latest stuff made it to next release).
>>
>> —
>> Erik Hatcher, Senior Solutions Architect
>> http://www.lucidworks.com
>>
>>
>>
>>
>> On Aug 5, 2015, at 11:09 AM, Noble Paul wrote:
>>
>> I have created the l
d the lucene_solr_5_3 branch.
> If anything new must go into 5.3 release please communicate it here
> and commit to the new branch as well
>
> @uwe, @sarowe , can someone help me setup jenkins for the same.
> --Noble
>
> On Wed, Aug 5, 2015 at 7:27 PM, Varun Thacker
> w
com/>
> On Aug 5, 2015, at 11:09 AM, Noble Paul wrote:
>
> I have created the lucene_solr_5_3 branch.
> If anything new must go into 5.3 release please communicate it here
> and commit to the new branch as well
>
> @uwe, @sarowe , can someone help me setup jenkins for the
Ok. Many thanks!
I was not sure, I think I removed the workspaces using the Gui after disabling
them. I just wanted to be sure we not run out of disk space.
Uwe
Am 7. August 2015 21:02:39 MESZ, schrieb Steve Rowe :
>
>> On Aug 7, 2015, at 2:50 PM, Steve Rowe wrote:
>>
On Aug 5, 2015, at
> On Aug 7, 2015, at 2:50 PM, Steve Rowe wrote:
>
>>> On Aug 5, 2015, at 3:10 PM, Uwe Schindler wrote:
>>>
>>> Steve: For ASF Jenkins, it would be ideal to rename the preexisting 5.2
>>> jobs and simply change the branch in the subversion settings. Before doing
>>> that, be sure to delete th
created the lucene_solr_5_3 branch.
If anything new must go into 5.3 release please communicate it here
and commit to the new branch as well
@uwe, @sarowe , can someone help me setup jenkins for the same.
--Noble
On Wed, Aug 5, 2015 at 7:27 PM, Varun Thacker
wrote:
> Hi Noble,
>
> I
> On Aug 5, 2015, at 3:25 PM, Steve Rowe wrote:
>
> Uwe, I don’t think renaming the preexisting 5.2 jobs is ideal, because
> preexisting release branch jobs can have stale config (inactive jobs’ configs
> don’t always get updated when other jobs’ configs do). When setting up
> release branch
lr_5_3?
>>>
>>>
>>>
>>> Thanks!
>>>
>>>
>>>
>>> Upayavira
>>>
>>>
>>>
>>> On Wed, Aug 5, 2015, at 04:30 PM, Upayavira wrote:
>>>
>>>> I need to update CHANGES.txt to
anks!
>>
>>
>>
>> Upayavira
>>
>>
>>
>> On Wed, Aug 5, 2015, at 04:30 PM, Upayavira wrote:
>>
>>> I need to update CHANGES.txt to account for a number of bug fixes
>>> to the
>>>
>>> angular UI. I'll add
o update CHANGES.txt to account for a number of bug fixes to
>the
>> angular UI. I'll add a single entry to account for them all.
>>
>> Upayavira
>>
>> On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote:
>> > I can work on setting up 5.3 release branc
On Wed, Aug 5, 2015, at 04:30 PM, Upayavira wrote:
> I need to update CHANGES.txt to account for a number of bug fixes to the
> angular UI. I'll add a single entry to account for them all.
>
> Upayavira
>
> On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote:
> > I
Noble Paul [2015-08-05 17:09]:
If anything new must go into 5.3 release please communicate it
here
What are the chances of getting the second patch from SOLR-7639
included in this release? It adds the missing pieces (support for
the `boost` parameter and exclusion of the current document from
.de
> eMail: u...@thetaphi.de
>
>
>> -Original Message-
>> From: Steve Rowe [mailto:sar...@gmail.com]
>> Sent: Wednesday, August 05, 2015 5:16 PM
>> To: Lucene Dev
>> Cc: Uwe Schindler; Noble Paul
>> Subject: Re: 5.3 release
>>
>> I c
.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Steve Rowe [mailto:sar...@gmail.com]
> Sent: Wednesday, August 05, 2015 5:16 PM
> To: Lucene Dev
> Cc: Uwe Schindler; Noble Paul
> Subject: Re: 5.3 release
>
&g
;> On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote:
>>> I can work on setting up 5.3 release branch jobs on ASF Jenkins later
>>> today if Uwe doesn’t beat me to it. - Steve
>>>
>>> > On Aug 5, 2015, at 11:09 AM, Noble Paul wrote:
>>> >
&
er of bug fixes to the
>> angular UI. I'll add a single entry to account for them all.
>>
>> Upayavira
>>
>> On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote:
>>> I can work on setting up 5.3 release branch jobs on ASF Jenkins later
>>> today i
wrote:
>> I can work on setting up 5.3 release branch jobs on ASF Jenkins later
>> today if Uwe doesn’t beat me to it. - Steve
>>
>> > On Aug 5, 2015, at 11:09 AM, Noble Paul wrote:
>> >
>> > I have created the lucene_solr_5_3 branch.
>> > If anythi
I need to update CHANGES.txt to account for a number of bug fixes to the
angular UI. I'll add a single entry to account for them all.
Upayavira
On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote:
> I can work on setting up 5.3 release branch jobs on ASF Jenkins later
> today if Uwe d
I can work on setting up 5.3 release branch jobs on ASF Jenkins later today if
Uwe doesn’t beat me to it. - Steve
> On Aug 5, 2015, at 11:09 AM, Noble Paul wrote:
>
> I have created the lucene_solr_5_3 branch.
> If anything new must go into 5.3 release please communicate it here
I have created the lucene_solr_5_3 branch.
If anything new must go into 5.3 release please communicate it here
and commit to the new branch as well
@uwe, @sarowe , can someone help me setup jenkins for the same.
--Noble
On Wed, Aug 5, 2015 at 7:27 PM, Varun Thacker
wrote:
> Hi Noble,
>
d
> wrote:
> >>> +1 to releasing 5.3, and thanks for volunteering!
> >>>
> >>> On Mon, Jul 27, 2015 at 10:56 AM, Noble Paul
> wrote:
> >>>> Hi,
> >>>> I would
PM, Adrien Grand wrote:
>>> +1 to releasing 5.3, and thanks for volunteering!
>>>
>>> On Mon, Jul 27, 2015 at 10:56 AM, Noble Paul wrote:
>>>> Hi,
>>>> I would like to volunteer myself as the RM for 5.3 release. I plan to
>>>> cut the 5.3
>> On Mon, Jul 27, 2015 at 10:56 AM, Noble Paul wrote:
>>> Hi,
>>> I would like to volunteer myself as the RM for 5.3 release. I plan to
>>> cut the 5.3 release branch by next Monday (03/Aug).
>>>
>>
oble Paul wrote:
>> Hi,
>> I would like to volunteer myself as the RM for 5.3 release. I plan to
>> cut the 5.3 release branch by next Monday (03/Aug).
>>
>> --
>> -
>> Noble Paul
>>
>>
+1 to releasing 5.3, and thanks for volunteering!
On Mon, Jul 27, 2015 at 10:56 AM, Noble Paul wrote:
> Hi,
> I would like to volunteer myself as the RM for 5.3 release. I plan to
> cut the 5.3 release branch by next Monda
Hi,
I would like to volunteer myself as the RM for 5.3 release. I plan to
cut the 5.3 release branch by next Monday (03/Aug).
--
-
Noble Paul
-
To unsubscribe, e-mail: dev
33 matches
Mail list logo