release candidate

You are currently browsing articles tagged release candidate.

3.1.0 Release Candidate

July 5, 2011 by Benedict Eastaugh | 3 comments

With today’s release of WordPress 3.2, I thought it would be good to get an updated version of Tarski out as soon as possible. To that end, here’s a release candidate build of Tarski 3.1.0.

There are a few changes from the beta version, the most obvious of which is the navigation, which now uses a more traditional dropdown style. As I’ve said before, this is not really to my taste, and has obvious usability problems for user agents without hover, but it seems to be what people want. I may release the expanding navbar code as a plugin for those who prefer it.

WordPress 3.2 is required to run this build of Tarski. If you try to use it with WordPress 3.1 or earlier it will throw errors and make your site unusable.

Tags: ,

Tarski 3.0 Release Candidate

March 15, 2011 by Benedict Eastaugh | 3 comments

Tarski 3.0 has actually been in the works since last August, which is really too long between releases. I had a bit of spare time this weekend so I decided to bite the bullet and bring Tarski up to date for WordPress 3.1.

The new features include support for menus and default headers; however, migrating your current settings will have to be done by hand, as I just don’t have the time to write or maintain an automatic upgrade routine. It shouldn’t take long to fix things to your liking, and the benefit is full compatibility with the core WordPress functionality.

I’d really appreciate it if you could download and install the release candidate. Andreas Beer has kindly been helping me test it, so it should be relatively bug-free by now. Testing and reporting bugs is not just a favour to me, but a boon to all Tarski users.

Update: thanks to everyone who provided feedback. Tarski 3.0.0 is now available for download.

Tags:

2.6 Release Candidate 2

December 21, 2009 by Benedict Eastaugh | 13 comments

With WordPress 2.9 out of the door, I figured it was time to get the ball rolling on the latest Tarski release. There are some fairly extensive improvements to some areas of the internals, so I would very much appreciate some testing before I release the final version.

Highlights of the changes include drawing header images and alternate styles from child themes, support for the new post thumbnails, and a switch to the HTML5 DOCTYPE.

If you test it, can you send me the string of your tarski_options option both before and after the upgrade? You can get it from your database by running the following SQL query on the database where WordPress is installed.

SELECT option_value FROM wp_options WHERE option_name = 'tarski_options';

Thanks!

Update

Found some bugs in the upgrade routine already. RC2 is now out, use that instead.

Tags: , ,

Since the core team decided to do another release candidate, I thought I’d put one out too. Get it while it’s hot.

Tarski 2.4 RC2 has much better trackback support, adds an extra save button to the bottom of the options page, and improves the update notifier’s HTTP transport checking. There are also various bits of refactoring that shouldn’t impact on the user experience. I should also note that the tag is on GitHub if you want to grab it that way.

December 10, 2008 by Benedict Eastaugh | Permalink

WordPress 2.7 is going to be released very soon, and a pretty stable release candidate is available, so now seems like an appropriate moment to put an RC of our own up for download.

Tarski 2.4 RC1 is essentially feature-complete; it will only work on WordPress 2.7, so if you have WordPress 2.6 or earlier, don’t install this version of Tarski. Bug reports are extremely welcome and should be posted on the forum.

Update: Ryan Boren tells us that “The final release of 2.7 won’t be here until next week.” Tarski 2.4 will follow shortly after that.

December 3, 2008 by Benedict Eastaugh | 4 comments

I don’t usually publicise release candidate downloads, but because Tarski 2.3 includes some fairly major changes to its upgrade process, I thought it could benefit from wider testing than I can manage alone.

The usual caveats about pre-release software apply: don’t use it on a production site, run it locally or on a development server with a copy of your production database. If you have Subversion, you can get it from our svn trunk.

Please post any bugs or feedback on the forum.

August 3, 2008 by Benedict Eastaugh | 3 comments