Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Date: Fri, 8 Jul 2011 20:19:53 +0300
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: users@subversion.apache.org
Subject: Testing 1.7 pre-releases Re: Trials with memcached
Message-ID: <20110708171953.GC12468@daniel3.local>
References: <83C4EC368F9D4E4E9917570F91F240AFBB78AC@cbr-exch-be1.cea.com.au>
 <20110707235912.GC5347@daniel3.local>
 <sig.1170f61dcd.83C4EC368F9D4E4E9917570F91F240AFBB78B2@cbr-exch-be1.cea.com.au>
 <20110708005812.GB6640@daniel3.local>
 <sig.01702bc81c.sig.0170c26834.83C4EC368F9D4E4E9917570F91F240AFBB78B4@cbr-exch-be1.cea.com.au>
 <20110708091305.GE31699@ted.stsp.name>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110708091305.GE31699@ted.stsp.name>
User-Agent: Mutt/1.5.20 (2009-06-14)

Stefan Sperling wrote on Fri, Jul 08, 2011 at 11:13:05 +0200:
> Doing pre-release testing is a great service to the community.
> For us, it is a lot easier to handle problems before the release,
> and we can respond to problem reports a lot quicker.
> 
> After release we are bound by compatibility guarantees that
> sometimes make bug fixing a little more painful. And you might
> have to wait for weeks for enough fixes to accumulate before
> a new patch release is issued that addresses your particular problem.
> 
> You will likely upgrade your setup to Subversion 1.7 eventually.
> Any problems that show up which are specific to your setup will
> have to be dealt with at that point. It's easier to spot and fix
> problems now, while you're not running 1.7 in production and while
> we're still moving towards the 1.7.0 release.