subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@gmail.com>
Subject Re: Time for 1.6.18?
Date Mon, 06 Feb 2012 20:46:43 GMT
On Mon, Feb 6, 2012 at 15:22, Trent Nelson <trent@snakebite.org> wrote:
> On Mon, Feb 06, 2012 at 11:39:13AM -0800, Hyrum K Wright wrote:
>> On Mon, Feb 6, 2012 at 1:25 PM, Blair Zajac <blair@orcaware.com> wrote:
>> > With a fsfs corruption bug found and fixed this week [1], should we cut a
>> > 1.6.18?  1.6.17 was tagged 8 months ago.  If we don't cut a new release,
>> > then we should probably let downstream distributions know about the issue so
>> > they can patch their builds.
>>
>> I've got time this week if folks are interested in this.  Any other
>> pressing items for 1.6.18?
>
>    Any chance the mergeinfo memory leak fix could be included?  This

Strictly speaking, 1.6.x releases are for security/corruption types of
fixes. ie. very severe stuff.

>    issue is severely affecting one of my clients, and they're still
>    on 1.6.x at the moment.  If it could be included in .18, I won't
>    have to patch it manually :-)
>
>    Extract from 1.7.x's STATUS log w/ relevant revs below.

That said... this particular fix seems very low impact on the rest of
the release. I'm at least +0 on including it.

>...

Cheers,
-g

Mime
View raw message