List Info

Thread: proxy balancer backports for 2.2.3




proxy balancer backports for 2.2.3
user name
2006-07-26 15:22:17
Mladen Turk wrote:
> 
> There are lots of things to backport. IMHO its the
entire HEAD,
> and spread over the multiple svn commits.
> How we should deal with that?
> Having multiple backports or a single one?
> 
> The patches before my addition for cping/cpong, that
BTW is
> configurable, and as such bares no regression, are
tested but
> there were no backport requests for them, neither they
are
> backported, like Jim's hot standby, etc...
> 

we should simply update STATUS as usually... most of the
backports are self contained enough and non-dependent
to allow that, I think.

-- 
============================================================
===============
   Jim Jagielski   [|]   jimjaguNET.com   [|]   http://www.jaguNET.com/
	    "If you can dodge a wrench, you can dodge a
ball."
proxy balancer backports for 2.2.3
user name
2006-07-26 15:30:29
Jim Jagielski wrote:
> Mladen Turk wrote:
>> There are lots of things to backport. IMHO its the
entire HEAD,
>> and spread over the multiple svn commits.
>> How we should deal with that?
>> Having multiple backports or a single one?
>>
> 
> we should simply update STATUS as usually... most of
the
> backports are self contained enough and non-dependent
> to allow that, I think.
>

It looks like bureaucratic overhead to me 
But OK, we can have multiple STATUS entries.

Regards,
Mladen.



proxy balancer backports for 2.2.3
user name
2006-07-28 13:29:09
yeah, it's a bit of an overhead, but it allows
for one-to-one mapping of SVN commits to each new
feature. And it makes it easier for
people to follow what each smallish patch
does (and therefore +1 it) rather than wrapping
their heads around something larger.

On Jul 26, 2006, at 11:30 AM, Mladen Turk wrote:

> Jim Jagielski wrote:
>> Mladen Turk wrote:
>>> There are lots of things to backport. IMHO its
the entire HEAD,
>>> and spread over the multiple svn commits.
>>> How we should deal with that?
>>> Having multiple backports or a single one?
>>>
>> we should simply update STATUS as usually... most
of the
>> backports are self contained enough and
non-dependent
>> to allow that, I think.
>>
>
> It looks like bureaucratic overhead to me 
> But OK, we can have multiple STATUS entries.
>
> Regards,
> Mladen.
>
>
>

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )