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

Re: Mark Revision as production version

From: Pavel Lyalyakin <pavel.lyalyakin_at_visualsvn.com>
Date: Mon, 21 Aug 2017 15:27:53 +0300

Hello,

On Mon, Aug 21, 2017 at 2:58 PM, AD <aldafas_at_gmail.com> wrote:
>
> Hi,
>
> How to mark a specific revision as production version?
>
> here is our scenario:
> We have three teams: DEV , Quality and production.
>
> If DEV team develop a file called file.c and they moved it to production. It takes time to deploy it as it goes to quality team for testing then to production team for deployment. DEV continue modifying file.c.
>
> How can other team members know the revision moved to production.
>
> Is there a feature that allow production team to mark a specific revision as production version after deployment?
>
> Thank you

Why don't you use tags?

* TortoiseSVN Manual | Branching / Tagging:
  https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-branchtag.html
* SVNBook | Tags:
  http://svnbook.red-bean.com/en/1.8/svn.branchmerge.tags.html

--
With best regards,
Pavel Lyalyakin
VisualSVN Team
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3291062
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-08-21 14:28:41 CEST

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