- Original Message -
> On Oct 29, 2013, at 10:24 AM, Igor Galić wrote:
>
> >
> > Hello happy people o/~
> >
> > November is getting closer and that means we should look into getting
> > 4.1.0 out the door:
> >
> >https://issues.apache.org/jira/browse/TS/fixforversion/12324891
> >
On Nov 4, 2013, at 7:30 AM, Igor Galić wrote:
>
>
> - Original Message -
>> On Oct 29, 2013, at 10:24 AM, Igor Galić wrote:
>>
>>>
>>> Hello happy people o/~
>>>
>>> November is getting closer and that means we should look into getting
>>> 4.1.0 out the door:
>>>
>>> https://issu
On Nov 4, 2013, at 8:48 AM, James Peach wrote:
>>> appropriate.
>>
>>
>> So I took a look at our tickets, and it would seem that they haven't moved
>> much. Especially with the broken builds, I'd like to see those fixed /soon/
>> unfortunately, I don't have a platform to test on, as the breakag
On Nov 4, 2013, at 8:57 AM, Leif Hedstrom wrote:
> On Nov 4, 2013, at 8:48 AM, James Peach wrote:
>
appropriate.
>>>
>>>
>>> So I took a look at our tickets, and it would seem that they haven't moved
>>> much. Especially with the broken builds, I'd like to see those fixed /soon/
>>> unfo
Thanks, we don't see the traffic_servers restart for a couple of days So
when 4.1.0 is out i will try to compile this. version.
Sjaak
On 11/3/2013 21:45, Leif Hedstrom wrote:
On Nov 2, 2013, at 10:22 PM, Alan M. Carroll
wrote:
Sorry, running too many bugs. The fix is in TS-1424, commit f63b
+1
I think we should remove the code to be send these configuration options in a
cluster request. Reason for this are:
1. These options are already propagated in cluster config
2. Cleaner code, able to remove code and simplify the cluster request
3. Seems odd to me to pass around a subset of the
