[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Time for 1.6.18?

From: Greg Stein <gstein_at_gmail.com>
Date: Mon, 6 Feb 2012 15:46:43 -0500

On Mon, Feb 6, 2012 at 15:22, Trent Nelson <trent_at_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_at_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.


Received on 2012-02-06 21:47:15 CET

This is an archived mail posted to the Subversion Dev mailing list.