Use tags in WP svn repo?

  • Any chance of getting the developers to tag WP releases in Subversion?

    I noticed you don’t use branches, but if it wouldn’t be too much trouble could you tag the revision that you deem final for a release? That way those of us who like to hack our core files (bad bad, I know ?? could check out the release version, and then later update to subsequent releases using the sooper-dooper power of svn.

Viewing 5 replies - 1 through 5 (of 5 total)

  • I agree. What would be the harm in doing a little ‘svn cp https://svn.automattic.com/wordpress/trunk https://svn.automattic.com/wordpress/tags/1.5.1.3’. You’d think you guys would want it too. That is, after all, what the directory is there for.

    Additionally, it would be nice if you guys did your “1.6 ALPHA-DO-NOT-USE” work somewhere other than the trunk, ideally the branch directory since that’s what it’s there for as well. I’ve spent the day trying to figure out how to get access to my blog again after accidentally updating to some sort of alpha work going on in the trunk that involves access modifications and some new user_metadata table.

    oops, i guess it’s there. not sure why i didn’t see it when i looked before..

    There are branches when necessary, and all the releases are tagged.

    The trunk is for unstable, latest and greatest work. We don’t need an ‘unstable’ branch to hold the 1.6 stuff, that’s exactly what the trunk is for.

    Don’t run the latest svn trunk unless you really know what you’re doing. Even then, don’t expect to get support for it at the forums.

    Supported Versions of WordPress do not include SVN check-outs, as has been indicated.

    There’s much debate as to how individual projects should develop in Subversion. The model chosen by the WordPress developers is to do everything in the trunk. This is unlikely to change.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Use tags in WP svn repo?’ is closed to new replies.