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

Re: fixing bug in multiple releases

From: Vikrama Sanjeeva <viki.sanjeeva_at_gmail.com>
Date: Wed, 21 Apr 2010 16:48:05 +0300

On Wed, Apr 21, 2010 at 3:42 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:

> Vikrama Sanjeeva wrote:
>
>>
>> Also, in case of web-applications what is the best practice to deploy
>> REL-1.7 on production ? Do we replace whole REL-1.6 code with REL-1.7 or
>> just update the production with modified binaries of REL1.7 ?
>>
>
> Normally you would want to work in a way that gives you a known 'roll-back'
> state in case the next change introduces problems. If you don't keep a
> whole release together you'll have to track the individual changes to know
> how to reproduce the last working state.
>
> --
> Les Mikesell
> lesmikesell_at_gmail.com
>
>
>
So you actually mean that for every change (big in size like 5-10+ files)
whole code should be replaced with new release, while keeping an option of
"roll-back" ?

Bye,
Viki.
Received on 2010-04-21 15:48:36 CEST

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

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