Add stable tag to SVN

[dustyakubra]

​Updating wordpress via svn is ​the hip thing to do these days (because it's about a million times easier than the usual way.) However, the guides I've seen so far all tell users to use wordpress trunk, and that's just stupid!

$ svn switch ​http://svn.automattic.com/wordpress/tags/2.0.7

is far longer than

$ svn up

so convincing users to do that would be difficult. What I would suggest is a "stable" svn tag - or you could call it "release" or whatever, but basically after implementing that, we can contact the authors of guides on using SVN to update Wordpress and encourage them to change to using the stable tag.

[foolswisdom]

Closing as WONTFIX for now.

Thank you for participating in WordPress!

There is also ​http://svn.automattic.com/wordpress/branches/2.0 , but I appreciate that is not your point.

This was discussed in September, ​wp-hackers SVN: /branches/stable/
and it seemed that there was technical problems. If you have known of another project this does this, and can find out the details that would likely help.

---

Matt's opinion near the end of thread was:
'At the end of the day, you probably don't want fully automatic upgrading as you don't know if the "stable" release of 2.1 (or 2.0) is going to break something you have.

My best guess would be a well-scripted way to SVN SWITCH several installs would be the safest.'

[AaronCampbell]

I agree that this would be a great feature to have. I know that phpMyAdmin does this, and if someone wants me to, I'll try to find out how they set it up.

[DD32]

Replying to AaronCampbell:

I know that phpMyAdmin does this, and if someone wants me to, I'll try to find out how they set it up.

I just checked out how PHPMyAdmin does it.
They simply delete the current stable tag when a new stable comes out, and tag the new stable as stable. You can see that by pulling up the SVN Logs for ​https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/tags/STABLE

At present i believe its still a wontfix situation, Tags are designed to be snapshots in time, not continuous rolling code like Branches. If the core devs feel like setting it up and maintaining it, I'm sure it'll happen, I'll leave it for a core dev to close however if need be.

[AaronCampbell]

It's not that huge of a deal, just means that automated upgrades take some scripting. I do think it would be nice, but it's nothing I'm going to whine about.

[DD32]

just means that automated upgrades take some scripting. I do think it would be nice, but it's nothing I'm going to whine about.

Same here, It'd be useful, Esp when including WordPress as a external item in another SVN repo, But in the end it comes down to someone having to maintain it :)

[lloydbudd]

Still no traction. Re-closing as WONTFIX.