Ubuntu 9.04 is here, and work continues

Ubuntu 9.04 is here, and work continues

Ubuntu 9.04 was released just over a week ago.  A release represents the public distribution of six months of serious work, a chance to show the world what we’ve been doing and how good it is.  It seems like a time to celebrate.  For me, it’s just as busy as ever.

The very next day I spent the greater part of the day putting out the new Wine release for beta testing.  It’s become a bit of a routine of mine every other Friday – wake up, download the new tarball, test build it, update the package, push it to the Wine team PPA for building, redownload it from there and put it on the budget dedicated server.  Then I’ll go read the Digg article and see people post how Wine is getting better all the time.  Every now and again I’ll have to do something special – this release, for instance, included the new icons I found.

I’m still not done with them though.  Nothing’s ever done, of course, but some days you spend 4 hours going over redesigns with another volunteer who probably wouldn’t be there without you.  This past week has given me a few more of those days.

I volunteered to teach an online class for Ubuntu Open Week on Friday.  I teach in real life professionally, however the experience on a muted IRC channel is quite different.  There’s absolutely no continuous feedback; no students slightly nodding their head or twisting it in confusion – just empty channel.

At first I thought I wouldn’t have much to talk about, but after taking a few questions I found myself running out of time.  I didn’t even get to talk much about some of the games projects I’ve been working on – people always have many questions about Wine.  They are, of course, completely right to do so.  You can read the session here.

Anyway, it’s getting late so I’ll make this brief: I spent the past week also catching up on 5-a-day bugs; the Wine package now ranks very highly on the list of packages with good bug reports (upstream percentage).  I’ve got about 5 different major Wine package changes around the corner, and I’ve decided to move forward with Wine beta releases in Karmic even though I can’t be 100% sure that Wine 1.2 will be released on time.


RonanMay 5th, 2009 at 4:13 am

Hello Scott,

You’re saying that for each new version, you “update the package, push it to the Wine team PPA for building, redownload it from there and put it on the budget dedicated server”.

1. That means the PPA is the preferred repository, right?
2. So is there any reason the recommended repo on wine download page is the budgetdedicated one? And why isn’t the PPA more publicized?

Thanks for the grrreat work,

YokoZarMay 5th, 2009 at 11:51 am

The PPA and budgetdedicated Repos are often identical. In most cases it doesn’t matter.

But note the workflow is that I upload it to the PPA before doing some minimal testing. In the case of a broken build dependency or a segfault or some substantial change to the package being wrong, a user on the PPA would get a bad package.

The repo is largely there (instead of, say, 2 PPAs) at this point for historical reasons. I started before there was such a thing as launchpad PPAs. Now it’s got 160,000 users, and I’m not sure how to properly migrate that many users to a PPA conveniently. So the path of least resistance is to just keep it going as is.

Leave a comment

Your comment