On Wed, Apr 21, 2010 at 8:13 PM, Les Mikesell wrote:
> On 4/21/2010 8:48 AM, 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 t
On 4/21/2010 8:48 AM, 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 ?
Nor
On Wed, Apr 21, 2010 at 5:18 PM, David Weintraub wrote:
> On Wed, Apr 21, 2010 at 4:27 AM, Vikrama Sanjeeva
> wrote:
> > Hi,
> >
> > Thanks Andy and David for your answers.
> >
> > As I said, it was just a supposition in a case where it becomes necessary
> to
> > fix all previous releases (for
On Wed, Apr 21, 2010 at 4:27 AM, Vikrama Sanjeeva
wrote:
> Hi,
>
> Thanks Andy and David for your answers.
>
> As I said, it was just a supposition in a case where it becomes necessary to
> fix all previous releases (for whatever reason). And in this case, I too
> think not to touch the tag itse
On Wed, Apr 21, 2010 at 3:42 PM, Les Mikesell 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 ?
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
Hi,
Thanks Andy and David for your answers.
As I said, it was just a supposition in a case where it becomes necessary to
fix all previous releases (for whatever reason). And in this case, I too
think not to touch the tag itself rather as per David's advise, branch the
tag 1.6, fix it and then r
On Mon, Apr 19, 2010 at 3:14 PM, Vikrama Sanjeeva
wrote:
> Suppose I have total 6 releases in /tag which are considered as stable
> releases. Now if, at 6th release we realize that there is a "bug" which
> should be fixed in all previous releases then what should be the strategy ?
> Is there any w
On Mon, Apr 19, 2010 at 15:14, Vikrama Sanjeeva wrote:
> Hi,
>
> Suppose I have total 6 releases in /tag which are considered as stable
> releases. Now if, at 6th release we realize that there is a "bug" which
> should be fixed in all previous releases then what should be the strategy ?
> Is th
Hi,
Suppose I have total 6 releases in /tag which are considered as stable
releases. Now if, at 6th release we realize that there is a "bug" which
should be fixed in all previous releases then what should be the strategy ?
Is there any way in SVN which allows to fix bug in all releases "at-a-ti
10 matches
Mail list logo
