Tarski’s changelog is now included in our svn repository, and having automated the process I’ve been updating the public one far more frequently. This means you can now see all the major changes without having to read the commit logs.
You are currently browsing articles tagged svn.
Putting out a new release of Tarski involves a fair few elements: tagging a new release in Subversion, creating a zip file and moving that to the downloads directory, updating the changelog, writing a release post, and finally updating the version feed so that existing users get notified about the new version.
All this is an increasingly automated process: I still have to publish the release post and update the changelog manually, but pretty much everything else can be done with a couple of tweaks to a config file and one shell command: rake tarski:update (actually you can just do rake since tarski:update is the default task).
You can now download my toolset from GitHub. Obviously to do so you’ll need Git, as well as Ruby and Rake to run it. If you have any questions, suggestions or bug reports, please let me know in the comments.
I’ve moved a couple of little plugins and templates onto our Subversion repository; you can find them in the extras directory. Hopefully this will make me more inclined to keep them updated—as they stand, they’ve been tested on the latest version of Tarski, but of course if you have any problems with them just post on the forum.
I wrote some .htaccess redirects, so all the old links should be redirecting (if you find any broken ones, please let me know). Tarski 2.0.5 should be out early next week, with the usual bug fixes and enhancements.
Just a quick note to say that if you’re testing WordPress 2.3, the trunk version of Tarski (1.7-alpha) is pretty stable, and is compatible with WP 2.3′s built-in tagging functions. I’ll be writing more about Tarski 1.7 and WordPress 2.3 over the next couple of weeks.