# How to deploy a tagged version instead of trunk?

**URL:** <https://www.ruby-forum.com/t/how-to-deploy-a-tagged-version-instead-of-trunk/91246>\
**Category:** Deployment\
**Created:** [April 5, 2007, 11:26pm UTC](https://www.ruby-forum.com/t/how-to-deploy-a-tagged-version-instead-of-trunk/91246 "2007-04-05T23:26:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeff](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e19b73/32.png) [@jeff](https://www.ruby-forum.com/u/jeff)\
**Post date:** [April 5, 2007, 11:26pm UTC](https://www.ruby-forum.com/t/how-to-deploy-a-tagged-version-instead-of-trunk/91246/1 "2007-04-05T23:26:43Z")

</div>

What is the best approach for deploying a tagged release to production  
instead of the trunk? This happens, for example, when you want to  
apply a small patch to production, but can’t deploy the entire trunk.

I took a look at this:

> **[QuotesQue.net is for sale | HugeDomains](https://www.hugedomains.com/domain_profile.cfm?d=quotesque.net)**
>
> Find a domain name today. We make it easy.

, but I am wondering if there are other options.

thanks,  
Jeff

---

<div class="post-metadata">

**Author:** ![jeff](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e19b73/32.png) [@jeff](https://www.ruby-forum.com/u/jeff)\
**Post date:** [April 6, 2007, 4:38am UTC](https://www.ruby-forum.com/t/how-to-deploy-a-tagged-version-instead-of-trunk/91246/2 "2007-04-06T04:38:16Z")

</div>

I wrote a blog post last month about this. Same idea, slightly  
different approach:  
[http://mojodna.net/2007/03/08/teach-capistrano-to-deploy-from-a-tag-](http://mojodna.net/2007/03/08/teach-capistrano-to-deploy-from-a-tag-)  
or-branch/

seth

---

<div class="post-metadata">

**Author:** ![jeff](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e19b73/32.png) [@jeff](https://www.ruby-forum.com/u/jeff)\
**Post date:** [April 6, 2007, 4:54pm UTC](https://www.ruby-forum.com/t/how-to-deploy-a-tagged-version-instead-of-trunk/91246/3 "2007-04-06T16:54:47Z")

</div>

Great, thanks… I like this approach better.

-jeff