Loves You Like a Kitten
Alright, here it is. The WordPress 2.1 compatible version of K2. We hope you'll help us test it to make sure that it is ready for prime time. As always, please use the issue tracker to let us know of bugs and such.
Version 0.95 will be the last version supporting WordPress below 2.1. After this we'll rip out all the 'legacy' stuff and focus on getting a 1.0 final out there in the wild.
Update: Steve wrote a guide to updating your K2 installation from v0.91.
Go download K2 v0.9.1, which fixes a number of bugs and is a recommended upgrade. Also available on the 0.9 tag of the subversion repository. This release is r150 on the main trunk for those interested.
Same procedure as last time James.
This release of K2 has been cleansed of all the bugs we know about. As such we consider this a 'stable release', which will go on to replace the ancient r167 release which has been doing the rounds for quite some time (and which is quite buggy actually). It is r113 in he current Subversion repository.
We will update this release with any necessary bug fixes on its own tag in our repository to keep it stable, while we move towards 1.0
The task now falls to you, our dear beloved user, to guide our hand to the chinks in its armor. There is bound to be something wrong somewhere, and we'd like nothing better than to carve it out and replace it with working parts.
This goes for everything from failing functionality to usability stupidity to 'ticks' and other minuscule oddness. The Issues database has a range of issues for milestone 1.0, please skim through those before you submit anything new.
Now please go download K2 0.9 and discuss away.
A few days ago Google launched Google Code Hosting, which features a subversion repository integrated with a bug tracker in a tight little package. For K2 we have so far been using a locally hosted subversion repository as well as a separate bug tracker (Mantis). And while both have worked quite well for our purposes, managing both is a hassle for various reasons.
So while it will set our revision history back to square one (or r1 as it were) and we have had to manually transfer our bug database, it seems to be a good decision in the long run to move K2 onto Google Code. So we've done that.
So from now on, you will find both the bug tracker and the subversion repository (which is a few revisions newer than the old repository, including support for allowing comment authors to edit their own comments after posting them) at our new kaytwo project home.
Therefor, from this day forth, please use the new bug tracker, which requires you to have a Google Account. I will see about closing the old one down for new bugs, but regardless we will be working from the new one.
All this means there may be some disruption in building the nightlies, and possibly some confusing when talking about revision numbers, we'll do what we can to make it work out as smoothly as possible.
Related to this we have set up some new version numbers in the issue tracker. They are fairly self-explanatory, but here goes:
Comments, question and discussion about this move goes into this forum thread.
PS: I'm updating the Wiki with a list of plugins support out of the box.
PPS: Wondering about the name? Google Code doesn't allow for two-letter project names. It is still called K2 for all intents and purposes.
Update: The old issues have now all been moved to the new bugtracker.
Zeo's set up a K2 nightly builds directory, which'll let you grab the latest version of K2 at any given time. As with direct access to the SVN, expect these to have problems!
PS: I'm closing comments on entries. Seems people can't stop posting support questions here. Please use the forums for that.