apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sander Striker" <s.stri...@striker.nl>
Subject Re: Backport policy, WAS: Re: svn commit: r678140 - /apr/apr/branches/1.3.x/memory/unix/apr_pools.c
Date Sat, 19 Jul 2008 12:25:24 GMT
On Sat, Jul 19, 2008 at 2:18 PM, Mladen Turk <mturk@apache.org> wrote:
> Sander Striker wrote:
>>>
>>> Modified:
>>>   apr/apr/branches/1.3.x/memory/unix/apr_pools.c
>>
>> This is just an example, I'm seeing a change land on trunk and a
>> minute later on 1.3.x.  What's our backport policy?  Do we just commit
>> to trunk and 1.3.x, or are we going to go a route where we get review
>> prior to backporting?  Think httpd STATUS...
>>
>
> I usually wait for a day or two before committing to 1.3.x or 1.2.x
> from trunk. This particular one is copy/paste typo and was not observed
> until Bojan and myself did some actual hard core testing.

Like I said, it was just an example.

> Think the backporting policy is "act responsible" right now,
> or am I wrong here?

Sander

Mime
View raw message