Where do you see that? For instance, the just previous MYSQL check uses 0 and
1, as does the backtrace check. I see 'yes' and 'no' used for things which are
enabled or disabled based on configuration, but things which are automatic
checks seem to use '0' and '1'.
On Thursday, March 3, 2016 3:
> On Mar 3, 2016, at 12:16 PM, a...@apache.org wrote:
>
> Repository: trafficserver
> Updated Branches:
> refs/heads/master 1d1cb8fae -> fbdf0221d
>
>
> TS-3977: Add cache-key-genid to experimental plugins.
> This closes #309.
>
>
> Project:
teven Hunter
wrote:
Stable_connection/StevenHunter
On Apr 24, 2015 11:09 AM, "Leif Hedstrom" wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide which,
> if any, of these should be moved to a stable state. Once stable, incompa
Stable_connection/
StevenHunter
On Apr 24, 2015 11:09 AM, "Leif Hedstrom" wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide
which, if any, of these should be moved to a stable state. Once stable,
incompatible changes within a majo
Hi,
+1 for background_fetch. I have tested it and its working fine. It is very
useful when the user request for large media files.
Regards,
Randeep
On Mon, Apr 27, 2015 at 8:39 PM, Sudheer Vinukonda
wrote:
> We have been running the below *experimental* plugins in production, so, I
> am
We have been running the below *experimental* plugins in production, so, I am
+1 on promoting these to stable (some of this have already received +1 votes,
but, I am listing them anyway, to possibly make the vote stronger ;) ):
- regex_revalidate- background_fetch- buffer_upload- esi
Thanks
>> On Apr 24, 2015, at 7:18, Leif Hedstrom wrote:
> >>
> >>
> >>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Below is a list of currently “experimental” plugins. We should deci
re we commit to
it being stable.
Just my $.01,
— leif
>
>> On Apr 24, 2015, at 7:18, Leif Hedstrom wrote:
>>
>>
>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom wrote:
>>>
>>> Hi all,
>>>
>>> Below is a list of currently “
I personally would like to see ts_lua go stable.
> On Apr 24, 2015, at 7:18, Leif Hedstrom wrote:
>
>
>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom wrote:
>>
>> Hi all,
>>
>> Below is a list of currently “experimental” plugins. We should decide whic
@apache.org>> wrote:
>>>
>>> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom >> <mailto:zw...@apache.org>> wrote:
>>>
>>>>
>>>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom >>>> <mailto:zw...@apache.org>> wr
t; On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom > <mailto:zw...@apache.org>> wrote:
>>
>>>
>>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom >>> <mailto:zw...@apache.org>> wrote:
>>>>
>>>> Hi all,
>>>>
>>
> On Apr 24, 2015, at 8:37 AM, Phil Sorber wrote:
>
> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom wrote:
>
>>
>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom wrote:
>>>
>>> Hi all,
>>>
>>> Below is a list of currently “exp
On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom wrote:
>
> > On Apr 24, 2015, at 8:09 AM, Leif Hedstrom wrote:
> >
> > Hi all,
> >
> > Below is a list of currently “experimental” plugins. We should decide
> which, if any, of these should be moved to a stabl
> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide which,
> if any, of these should be moved to a stable state. Once stable, incompatible
> changes within a major release would n
Hi all,
Below is a list of currently “experimental” plugins. We should decide which, if
any, of these should be moved to a stable state. Once stable, incompatible
changes within a major release would not be accepted. Being stable also means
that we expect it to be fully maintained and
On Apr 16, 2014, at 9:04 AM, Leif Hedstrom wrote:
>
> On Apr 16, 2014, at 8:58 AM, Shu Kit Chan wrote:
>
>> Hi,
>>
>> There are a few experimental plugins that I think should be deprecated. e.g
>> The lua plugin should be deprecated in favor of the newer
On Apr 16, 2014, at 7:58 AM, Shu Kit Chan wrote:
> Hi,
>
> There are a few experimental plugins that I think should be deprecated. e.g
> The lua plugin should be deprecated in favor of the newer ts_lua plugin.
IIRC you were going to compare the lua plugins? Can you share any notes?
On Apr 16, 2014, at 8:58 AM, Shu Kit Chan wrote:
> Hi,
>
> There are a few experimental plugins that I think should be deprecated. e.g
> The lua plugin should be deprecated in favor of the newer ts_lua plugin.
> The same can be said for the stale_while_revalidate in fav
Hi,
There are a few experimental plugins that I think should be deprecated. e.g
The lua plugin should be deprecated in favor of the newer ts_lua plugin.
The same can be said for the stale_while_revalidate in favor of the newer
rfc5861 plugin. During the recent summit in denver we also talked
when breaking the rules and not complying :-)
>
> Of these experimental plugins, I've starred the ones that I know to be
> deployed in production:
>
> * authproxy
> balancer
> buffer_upload
> channel_stats
> cus
On Sep 20, 2013, at 2:27 PM, Theo Schlossnagle wrote:
> experimental is experimental. No restrictions. Innovation comes more
> cheaply when breaking the rules and not complying :-)
Of these experimental plugins, I've starred the ones that I know to be deployed
in
Asked about this in IRC, but wanted to bring it to the list. For
experimental plugins, do we need to abide by the backward compatibility
rule in a stable release? Same question probably applies to
ts/experimental.h.
My opinion at first was no. It's experimental, duh! But the more I think
abo
On Sep 20, 2013, at 10:24 AM, Phil Sorber wrote:
> Asked about this in IRC, but wanted to bring it to the list. For
> experimental plugins, do we need to abide by the backward compatibility
> rule in a stable release? Same question probably applies to
> ts/experimental.h.
>
ng it to the list. For
> > experimental plugins, do we need to abide by the backward compatibility
> > rule in a stable release? Same question probably applies to
> > ts/experimental.h.
> >
> > My opinion at first was no. It's experimental, duh! But the more I thi
On Sep 20, 2013, at 11:24 AM, Phil Sorber wrote:
> Asked about this in IRC, but wanted to bring it to the list. For
> experimental plugins, do we need to abide by the backward compatibility
> rule in a stable release? Same question probably applies to
> ts/experimental.h.
>
On Feb 5, 2013, at 8:03 AM, Leif Hedstrom wrote:
> On 2/5/13 9:00 AM, James Peach wrote:
>> On Feb 5, 2013, at 5:41 AM, Leif Hedstrom wrote:
>>
>>
>>
>> b) would be my preference.
>>>> Mine too ;)
>>>>
>>>> I think the mo
On 2/5/13 9:00 AM, James Peach wrote:
On Feb 5, 2013, at 5:41 AM, Leif Hedstrom wrote:
b) would be my preference.
Mine too ;)
I think the move towards --enable-experimental-plugins on the buildbots might
give you exactly that: People owning up to (their?) code, fixing broken builds
or at
don't
>>> build (but then, how will someone test / fix / build those plugins?).
>>>
>>>
>>> b) would be my preference.
>>
>> Mine too ;)
>>
>> I think the move towards --enable-experimental-plugins on the buildbots
>>
>> b) would be my preference.
>
> Mine too ;)
>
> I think the move towards --enable-experimental-plugins on the buildbots might
> give you exactly that: People owning up to (their?) code, fixing broken
> builds
> or at the very least filing tickets.
>
Except t
On Monday, February 04, 2013 09:18:37 PM you wrote:
> On 2/2/13 4:47 AM, Igor Galić wrote:
> > Hey folks,
> >
> > just a heads-up: I put --enable-experimental-plugins in all our builds
> > and I'm expecting some massive failures all over the place.
> >
&g
On 2/2/13 4:47 AM, Igor Galić wrote:
Hey folks,
just a heads-up: I put --enable-experimental-plugins in all our builds
and I'm expecting some massive failures all over the place.
This code needs more exposure, and I thought I'd start by building it.
I'm not sure this
On 02/02/2013, at 3:47 AM, Igor Galić wrote:
>
> Hey folks,
>
> just a heads-up: I put --enable-experimental-plugins in all our builds
> and I'm expecting some massive failures all over the place.
>
> This code needs more exposure, and I thought I'd start by building it.
Good plan
J
Hey folks,
just a heads-up: I put --enable-experimental-plugins in all our builds
and I'm expecting some massive failures all over the place.
This code needs more exposure, and I thought I'd start by building it.
So long.
-- i
33 matches
Mail list logo
