My Life Stream
Awesome...Google Maps street view in Ventura CA. Now, I'm off to find our cars. 8 hrs ago

I think I’ve finally finished getting all of my themes…

1 year, 1 month ago
in Tweets
. Tags: , , , .

I think I’ve finally finished getting all of my themes and plugins straightened out on my site. It turns out Trac isn’t very user friendly when it comes to getting people to download. I ended up using a downloads plugin to help manage the downloads through wordpress itself. At least this way I don’t have to worry about having beta or bleeding edge updates on the main trunk where people would download them. One problem I’m having is svn is thinking apache is 301 redirecting my repos when I try to checkout, the easy fix was just checking out the /trunk and other directories after the URL, but what a pain, I’ll figure it out later. [Link] (0)

Viewing 5 Comments

    • ^
    • v
    What do you mean when you say:

    worry about having beta or bleeding edge updates on the main trunk where people would download them
    • ^
    • v
    I had planned to use the trunk for all downloads, you know the "zip archive". I could have placed pre-released plugins or themes in tags and then moved them into the trunk but it's easier to just keep it in the trunk for the brave to find and best to have the downloads easier to find and properly named.
    • ^
    • v
    Trac will offer Zip archives from the tags (or anywhere in your tree), it doesn't have to just be from the trunk.

    Also, to be consistent with standard SVN usage you would never move something from tags into the trunk. Trunk -> Branches -> Tags is the generally accepted convention.

    All new and ongoing development should be done in trunk, then branches should be made (which are basically snapshots of the trunk at that point in time - see WordPress branches for 2.1, 2.2, etc.). All new changes still only go into trunk, and branches are used for bug fixes / security updates, etc. (to the 2.2 branch in WP, for example, because the trunk code is currently 2.3).

    Finally, whenever you have a released version, you make a tag, which is (usually) a copy from the branch (ie: WP 2.2.1, 2.2.2, etc. are copies from the 2.2 branch) and then are never changed, so that you always have snapshots of what you released and do diffs, etc.
    • ^
    • v
    I understand how it works but I don't think everyone else knows, it doesn't matter too much since I never intended to implement that wacky method, I shouldn't have used "planned". And I only mentioned it because that's the only way I thought to handle the people who do not know the dev cycle or know where to get stable releases vs. simply using the only download link in the repo (which is on the trunk page). Shortly after posting that I noticed you can make zips of any archive but I'd never use it unless I could fix the name generation it uses.
    • ^
    • v
    Yeah, that's what I was wondering about the download thing, since anywhere (not just trunk) will auto-generate those zips for you, if you wanted to use that.

    If you want to use a custom name, then it might be best to manually make the archive and then you can always link to it from anywhere (on your site, the trac main page, etc.)

    Probably anyone who's going to bother to go into Trac and/or subversion has some idea of how it should work, but most people would probably rather just download it directly via a link from your site.

Trackbacks

close Reblog this comment
Powered by Disqus · Learn more
blog comments powered by Disqus