I speak an a user not a developer as I can't even spell PHP. Curiously enough, I have a draft post about this very subject with a working title of 'To SVN or not to SVN - that is the question'.
When I first migrated to Habari, there was a distinct feeling on being in on something was was being actively developed, rapidly moving, exciting and excuse the tired old cliche, bleeding edge. As formal releases of Habari are less frequent and exciting than a daily 'svn update' that could potentially break your blog, I simply couldn't resist the temptation for very long. So, I built a subversion client on Bluehost and tracked SVN head on a daily basis. From last February until now. Obviously I track the changes in trac so have an idea of what's in the pipeline. Often it is new functionality or fixes, I have been waiting for and only too eager to try out. Initially, I was afraid, desperately afraid - mainly of schema changes that would be released overnight break my blog and force me back to the dark side (textpattern, anyone ?) However, I soon realised that SVN HEAD was probably the safest place to be - most of the Habari developers are running it and if something goes pear shaped, it gets noticed pretty damned quickly (expletives in IRC) and guess what ? - those very same people are the very ones best placed to fix it. Well, it's only fair as one of them probably broke it in the first place :-) Seriously though, I can count the glitches in the fingers of one thumb where my blog has been inaccessible as a consequence of unning SVN HEAD. And the big plus is that you get to see (err, debug) that latest features as they roll off the conveyor belt. You are also free to test themes and plugins that (typically) are written for the latest version. HTH -- Andy On Jan 7, 10:39 pm, "Michael Harris" <[email protected]> wrote: > 2009/1/8 pepijn <[email protected]>: > > > > > on the site it says to get the latest svn use something like svn co > > <url> <path> > > this is okay for developers and people who want to update their local > > copy, but you should mention the svn export function, i don't > > want .svn folders al over the place! > > I'd recommend against exporting trunk, in general. While it is > relatively stable, features are often only partly implemented, bugs > may have been introduced etc, so you'll want to be able to upgrade > easily. If you're using a tag, export might be appropriate. > > -- > Michael C. Harris, School of CS&IT, RMIT > Universityhttp://twofishcreative.com/michael/blog > IRC: michaeltwofish #habari --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users -~----------~----~----~----~------~----~------~--~---
