Stable tag of plugin in the readme file

Question

If I am pushing a new version (v0.2) of my plugin (v0.1) on the repo, what does I do with the stable tag in readme file? Change it to v0.2?

What should come here? Clarifications please :)

Rarst · Accepted Answer · 2011-04-16 21:25:21Z

up vote 5 down vote accepted

Yes. You need to:

edited Apr 16 '11 at 21:25

answered Apr 16 '11 at 20:59

Rarst♦
41.5k230116

	I think it's recommended that the last step should be to update `trunk/readme.txt` to reflect the new stable tag. Otherwise you can get a possible race condition where the wp.org servers think there's a new tag to bundle, but it doesn't actually exist yet, because you haven't done the `svn cp` yet. – Dougal Campbell Apr 16 '11 at 21:20
	@Dougal Campbell I think refresh interval of repository is 15 minutes so order isn't particularly important and I didn't meant my answer to enforce any order... I will edit to change to unordered list. – Rarst♦ Apr 16 '11 at 21:25
	What's up with the order? Shouldn't I just commit everything to trunk and then copy over to a sub-directory in Tags? – Ashfame Apr 16 '11 at 21:30
	@Ashfame yes, that will work. I think what Dougal wanted to describe is that it can glitch if repository refresh happens after you change trunk but before you create target tag. Personally I think that is unlikely. – Rarst♦ Apr 16 '11 at 21:33
	@Rarst Even if that glitch occurs, it will be resolved in next refresh anyway, right? – Ashfame Apr 16 '11 at 21:37

Dougal Campbell · Answer 2 · 2011-04-16 21:28:25Z

I'd recommend this order of operations:

Update your plugin's .php file in trunk to reflect the new version, and commit
svn cp trunk tags/0.2
Edit tags/0.2/readme.txt and trunk/readme.txt to reflect new stable tag
svn commit -m "Tagging ver 0.2"

2 Answers