status of trunk (3)

Note: This is an old post in a blog with a lot of posts. The world has changed, technologies have changed, and I've changed. It's likely this is out of date and not representative. Let me know if you think this is something that needs updating.

I apologize for skipping last week's status of trunk.

Trunk is still unstable. I consider "trunk is stable" to mean that most things are re-implemented and it's usable. We're not quite there yet. I'm seeing occasional crashers (most of them my fault so far), there are a bunch of features that haven't been re-implemented (site search, channel search, playing through a playlist, setting preferences, ...), and there's still ui nits that need ironing out.

We're moving along, though it seems as if the progress comes in waves during the week. I think part of this is that we're all using git over svn and batching commits. I know I am.

I was gone all last week at OSCON, but I'm back again to help out with the push to Miro 2.0.

You can follow along in your story book with the Trac timeline.

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.