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

Re: Update a previous tag

From: Andy Levy <andy.levy_at_gmail.com>
Date: Thu, 3 Dec 2009 08:36:15 -0500

On Thu, Dec 3, 2009 at 06:49, welo <walid_alkaakati_at_yahoo.com> wrote:
> Hello,
>
> Iam planning a new repository layout as follows:
>
> DBUSER(1)
>   V2.5 --Branch
>      V2.5.1 --Release number
>          Packages
>          Triggers
>          Tables
>          .....
> DBUSER(2)
>  V2.5 --Branch
>       V2.5.1 --Release number
>          Packages
>          Triggers
>          Tables
>          .....
> DBUSER.....
>
> My question is suppose iam now in release  V2.5.5 and discovered a bug in release V2.5.1 how i propagate the fixing of the bug from release 1 to release 5 ? do i have to edit 5 releases ? .

If you change V2.5.1, it's no longer V2.5.1. It's a new release. You
can't have 2 different versions of your software "in the wild" with
the same version number. It's not a Subversion limitation, it's just
plain bad practice to do that.

Well, you can, but I don't want to be part of the group that has to
support such a decision.

Move forward. If someone is running V2.5.1 and encounters a bug that's
fixed in V2.5.5, upgrade them to V2.5.5. Or branch V2.5.1, call it
V2.5.1.1 or V2.5.1a and backport your fix to that line of code.

But don't ever reuse release numbers.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2426701

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-12-03 14:36:32 CET

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