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

Re: svn commit: r37902 - trunk

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 29 May 2009 21:45:37 -0400

On Fri, May 29, 2009 at 7:37 PM, Hyrum K. Wright <hyrum_at_hyrumwright.org> wrote:
> On May 29, 2009, at 5:44 PM, Arfrever Frehtes Taifersar Arahesis wrote:
>
>> 2009-05-29 23:54:58 Hyrum K. Wright napisał(a):
>>> There are a couple of fixes already merged to 1.6.x which fix bugs
>>> which we've been hearing about a lot lately (I'm looking at you,
>>> r37894).  If nobody objects, I'd like to cut 1.6.3 early this
>>> upcoming
>>> Wednesday, in an effort to get these fixes out there quickly.  I
>>> realize this comes pretty quickly on the heals of 1.6.2, but I feel
>>> the fixes are important enough to do a quick release.
>>
>> IMHO it would be better to release 1.6.3 30 days after the release
>> of 1.6.2.
>
> Would you care to #define that magic number?  :)

Barring some kind of data loss bug, there is something to be said for
just sticking to a rhythm. I agree that some of the fixes since 1.6.2
are particularly high value, so I would not object to a release next
week. That said, I also think it could wait another week or 2 as
planned to see what other fixes get in and to allow for proper review
of anything else.

There was that thread on the problem with copy, as an example. Will
it be fixed in the next week? I'd guess no, but maybe it is getting
some attention now. Were a fix to come in say in a week it sure would
be nice to get it in to 1.6.3 (as well as a 1.5.x release).

Anyway, no objections from me, just saying that I also think there is
merit in sticking with the "plan".

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2357038
Received on 2009-05-30 03:46:25 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.