Title: Tags on Subversion
Last modified: September 1, 2016

---

# Tags on Subversion

 *  [philliplord](https://wordpress.org/support/users/philliplord/)
 * (@philliplord)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/)
 * This is a very nice plugin, and thank you for releasing it.
 * It would be nice if version releases were tagged in subversion, as this would
   make upgrading easier for me.
 * [https://wordpress.org/plugins/wp-fastest-cache/](https://wordpress.org/plugins/wp-fastest-cache/)

Viewing 15 replies - 1 through 15 (of 22 total)

1 [2](https://wordpress.org/support/topic/tags-on-subversion/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/tags-on-subversion/page/2/?output_format=md)

 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7717597)
 * How can I do that?
 *  [Beherit](https://wordpress.org/support/users/beherit/)
 * (@beherit)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7717734)
 * +1, now we don’t have stable release channel – all changes are live on production.
   [@emrevona](https://wordpress.org/support/users/emrevona/) if You use TortoiseSVN
   just click RMB on trunk folder and chose “Branch/tag” option. Then You need put
   revision to tag and confirm it 🙂 And the most important: in readme.txt You need
   to change “Stable tag” from trunk to some version that You taged.
 *  Thread Starter [philliplord](https://wordpress.org/support/users/philliplord/)
 * (@philliplord)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7717737)
 * After you have made the a commit which releases a new version, you just copy 
   the whole of trunk to tags with the appropriate release version.
 * See, for example:
 * [http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html](http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html)
 * svn copy [http://svn.example.com/repos/calc/trunk](http://svn.example.com/repos/calc/trunk)\
   
   [http://svn.example.com/repos/calc/tags/release-1.0](http://svn.example.com/repos/calc/tags/release-1.0)\-
   m “Tagging the 1.0 release of the ‘calc’ project.”
 * As beherit says, you also need to update the readme.txt tag which wordpress.org
   uses.
 * Then I can work out the current release version and the commit that caused simply
   from subversion. I normally install plugins using svn, so this makes it very 
   easy for me to update. As a side effect, it also makes you version history a 
   little better.
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7717756)
 * Actually I don’t release new version after little changes.
 * [https://wordpress.org/plugins/wp-fastest-cache/stats/](https://wordpress.org/plugins/wp-fastest-cache/stats/)
 * I released the previous new version at 12th July. After 12th July I have implemented
   new features. And I released the latest version at 29th August. During 47 days
   I was waiting for any issue. and I released new version when I am sure that there
   is no problem.
 * Isn’t it a good way?
 *  [Beherit](https://wordpress.org/support/users/beherit/)
 * (@beherit)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7720290)
 * You are wrong. For example: after release version 0.8.6.0 You have done a lot
   of commits, when someone clicked to download version 0.8.6.0 really download 
   trunk folder with latest commits. Now we have version 0.8.6.1 and if You for 
   mistake commit a very big bug that broken site then this bug will have a lots
   of users e.g. those who just update from version 0.8.6.0 or those who just download
   Your plugin.
 *  Thread Starter [philliplord](https://wordpress.org/support/users/philliplord/)
 * (@philliplord)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7722093)
 * I am running of trunk at the moment, which isn’t ideal, no. As Beherit says, 
   so are many other people.
 * A more normal workflow would be this….
 * On trunk:
    commit, commit, commit, decide that you have reached a release commit
   last documentation update for release (including stable tag update) copy trunk
   to tags with the new release version
 * start commits for new version.
 * If you want to wait for issues before release, then yes you can do this — you
   can make the svn copy from the last commit you want to be in the release, even
   if it is not the most recent commit on trunk.
 * For my own usage, I would rather use this plugin from a stable release rather
   than directly from trunk.
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7722365)
 * I prefer agile development. What do you think about it?
 *  [Beherit](https://wordpress.org/support/users/beherit/)
 * (@beherit)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-7722573)
 * [@emrevona](https://wordpress.org/support/users/emrevona/) You can use agile 
   development or what You want – the problem is that You not tag version that You
   release and user don’t download specific version but the latest version from 
   trunk (with latest commits, not tested, unstable etc).
 *  [Beherit](https://wordpress.org/support/users/beherit/)
 * (@beherit)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-8550620)
 * [@emrevona](https://wordpress.org/support/users/emrevona/) Still there is no 
   tags and we have beta-unstable function in trunk which You are tagged as stable
   tag 🙁
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-8553702)
 * noo. Now it is stable version. I changed the files many times ago.
 *  [Beherit](https://wordpress.org/support/users/beherit/)
 * (@beherit)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-8553729)
 * I think You don’t understand how WordPress SVN works 🙂 In readme.txt You should
   add tag number in “Stable tag” – this is stable tag for Your plugin version, 
   not WordPress version as You already set. For now You should change “Stable tag:
   4.7” to “Stable tag: 0.8.6.3” and then tag latest revision in trunk folder as“
   0.8.6.3”. For now download button points to latest files from trunk folder.
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-8553751)
 * you are %100 right 🙂 I don’t know how to use. If you teach me, I will be so 
   happy.
 *  [Beherit](https://wordpress.org/support/users/beherit/)
 * (@beherit)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-8555494)
 * [@emrevona](https://wordpress.org/support/users/emrevona/) which software are
   You use? Which OS? 🙂 If You tell me I will send to You a small FAQ 😉
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-8555577)
 * please help me via email 🙂 [fastestcache@gmail.com](https://wordpress.org/support/topic/tags-on-subversion/fastestcache@gmail.com?output_format=md)
 *  [Beherit](https://wordpress.org/support/users/beherit/)
 * (@beherit)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/tags-on-subversion/#post-8790828)
 * [https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/#task-3](https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/#task-3)

Viewing 15 replies - 1 through 15 (of 22 total)

1 [2](https://wordpress.org/support/topic/tags-on-subversion/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/tags-on-subversion/page/2/?output_format=md)

The topic ‘Tags on Subversion’ is closed to new replies.

 * ![](https://ps.w.org/wp-fastest-cache/assets/icon-256x256.png?rev=2064586)
 * [WP Fastest Cache - WordPress Cache Plugin](https://wordpress.org/plugins/wp-fastest-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-fastest-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-fastest-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-fastest-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-fastest-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-fastest-cache/reviews/)

 * 22 replies
 * 3 participants
 * Last reply from: [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/tags-on-subversion/page/2/#post-8814235)
 * Status: not resolved