Comments on: Releasing New Versions of your WordPress Plugins Tech Tips, Reviews, Tutorials, Occasional Rants Sat, 31 Aug 2013 15:50:35 +0000 hourly 1 By: Everett - Fri, 06 Jan 2012 06:30:55 +0000 I should point out the super-fast version for those of you who are daring enough to try it:

1. Make your edits, update your readme.txt to reflect the new version, and update the “stable tag” to this new version (yes, update it BEFORE that directory exists).
2. Commit your changes (the head is ON now…)
3. Quickly copy over the trunk to the tags folder as outlined above, e.g.
svn copy

That works, but it’s a potentially problematic: if WordPress scans its directory before you’ve copied over the trunk, it will package up the code at the head in the TRUNK. At that moment, that code should be identical to what you’re copying into the new tags directory, but you have to ask “when will WP re-scan the repo?” because you definitely don’t want the code at the HEAD to be in your zip file after you’ve made other changes.

By: steve Tue, 06 Sep 2011 01:31:22 +0000 dude, thanks, I was going bonkers .. and I’ve had years of experience in svn.. but my current f/t job uses git, so I guess I was resisting this…
anyway, damn, the instructions at: absolutely steered me in the most confusing directions .. it asks you to work in your local copy and then manually create the new directory under tags and then manually copy your files in there, and then do the svn cp and things just didn’t work ..

After reading your documentation, I realized I could simply do a “svn copy trunk tags/tagnum”, (after checking out my repos into a local working copy of course)… talk about easy frackin button!

By: Lucas Hoezee Fri, 15 Jul 2011 21:40:59 +0000 Ok … Just wanted to return back to say it’s all working. Thanks again!

By: Lucas Hoezee Fri, 15 Jul 2011 21:00:52 +0000 Thanks for the video. You are right, their documentation is terrible. I will try out what you suggested and let you know the outcome!