Thanks to Google Code, we now have a Tarski Subversion repository. The trunk can be accessed via the web at http://tarski.googlecode.com/svn/trunk/, and the Google Code project for Tarski is here.
Those with svn installed on the command line can use the following command to checkout the latest and greatest (and use-at-your-own-risk) version of Tarski:
svn checkout http://tarski.googlecode.com/svn/trunk/ tarski
If anyone feels like explaining what tags and branches are in Subversion and how I should be using them for Tarski, that’d be awesome. Revision 2 on the repository is 1.3, and revision 3 is 1.4.
.pot files will be available as a branch as soon as I figure out how to get ZigVersion to do them. :-)
Tags: Google Code, source, Subversion
9 comments
June 13, 2007 at 11:32 am
Pingback from Extralogical · Adding Custom WordPress Hooks
April 16, 2007 at 2:36 am
Patis
Chapter 4 of the Subversion Book talks about branches and tags. In my opinion, for the purposes of a project like Tarski a simple way to look at these two elements is the following:
Use tags to capture specific Tarski releases. For example, make a SVN copy of the subversion revision number 2 to something like
tags/tarski-1.3. Make a SVN copy of subversion revision number 3 totags/tarski-1.4. This will give you a nice history of the project and a simple way to manage releases.By the way, usually there are many subversion revisions in between tag releases; I guess you have none between Tarski 1.3 and 1.4 just because you are starting with subversion.
I wouldn’t worry with branches at this time. If Tarski had multiple developers you could use them to track different development streams and get into the whole business of merging branches, not necessarily a trivial exercise. For bug fixing you can adopt a simple strategy: bugs are fixed in the current release, something which I believe you have done with Tarski up until now. I see no reason to change it for now.
Anyway, just my two cents. I certainly welcome the SVN repository for Tarski. Thanks for the good work.
–
Patis
April 16, 2007 at 2:45 am
Chris Sternal-Johnson
Cheers, Patis. I renamed tags ‘releases’ to be a little more self-explanatory. I’d go back and add all the versions from 1.0 onwards, but it’d be little use I’d imagine - I just put 1.2.5 and 1.4 up.
April 16, 2007 at 3:17 am
patis
On a side note: comments are previewed in real time very nicely but at the end they are not displayed as originally intended. In my first comment “Subversion Book” was a link to the site, and I used bullets for my two paragraphs on tags and branches. None of this finally made it to the comment even though it was nicely displayed in the preview 8-|
Lets see, this is the Tarski site, and this is bold face … nice preview, let’s see how it goes at the end.
April 16, 2007 at 4:32 am
Chris Sternal-Johnson
Yeah, unfortunately, the preview isn’t a live AJAX preview, so it’s fairly unintelligent. It’d be great if someone coded a JavaScript live preview that obeyed the WordPress “Allowed Tags” settings without having to hit the server every two seconds via AJAX.
April 17, 2007 at 7:44 pm
Erik Scrafford
To create branches in ZigVersion, you can connect to http://tarski.googlecode.com/svn/ , create a directory named branches at the top, and then drag trunk to branches - it will ask you if you want to copy or move (you want to copy), and give it a branch name other than trunk. ;)
April 17, 2007 at 8:06 pm
Chris Sternal-Johnson
That’s a handy tip, thanks Erik. I’d been using the command line to do it…
April 28, 2007 at 8:43 am
Free Net Publishing
So far I’m using the Semiologic template on my article blog… but I found Tarski to be lean and elegant. Will give it a try.
-Robert
May 1, 2007 at 10:01 pm
Wptr Themes
Perfect, thanks…