In the sprit of “dog food” and all that, overnight I upgraded joshix.com to the razor edge of Habari svn. I’d been running on the stable 0.5.2 release here, but the urge to develop and test against my own little use case is too strong.
This also brings the most-current version of the sp theme to this site, instead of the randomly-hacked/patched/reconstituted custom version I had been using. Sp v0.5, compatible with the `stable’ Habari 0.5.2 release, will see no further updates of any kind.
The version you see here is, roughly, sp 0.6.4RC. However, since we’re tracking the moving target of the Habari repository tip, I’m dropping all the resolution from our version number for now. This release of sp is numbered 6, and that ‘version number’ will reflect only the targeted Habari release series.
Sp v6 is for use with tonight’s nightly, Habari svn rev 2971, and up. It’s available from our dev server, either at the link above, or via git clone git://labs.utopian.net/sp.
Great news. I always track SVN HEAD and one (minor) frustration is that themes for the latest formally released, stable version of Habari don’t always work when living on the bleeding edge.
@Andy C: It was a post of yours on habari-users a day or two ago that reminded me “oh yeah, I’ve been meaning to go to svn…”. So thanks for both the comment, and the nudge.
I seem to notice the problem you mention in both directions; more plugins seem to target the latest habari, while themes are more apt to be aimed at the last stable version. For a while in sp the same code could run on both stable and svn, but in the end I was always coding in control flow, and habari isn’t even 1.0 yet anyway. For new software like this, why not clean, rather than compatible? (, I decided.)
…considerable scope for additional functionality in the future.ThemesJosh Wood makes the decision to track the latest Habari release (using subversion) and does everyone a favour by providing versions of hi…