I'm back in the states and now focusing on dotlrn. (As far as eLane, Rocael and I are waiting for some respondes from the other partners and then he'll be posting stuff).
I'm attaching a document that show the bugs that are labeled as "required for Sloan upgrade" by Dee. About half of them are assigned. The ticket tracker does a lot of automatic tracking and reminders - this works to some level. I'll be using and updating the "priority" buglist as a way to push forward the bugs that are important but also escape this process. There are about 30 bugs currently and this list will evolve.
As far as the assignees, I'll be following up with those that are assigned (about half). For the ones that are not assigned, I'll try first for the package owner and then work from there.
The release? At a chat a few weeks ago, we had a long discussion about what and how we should do about the the release criteria. We went back and forth and also called in Joel and finally decided to release at about the time Heidelberg launched. Carl was going to check with the other university that was going to use the release in the short term (Manheim) and make sure they are on board. Since then, there are a few other high-priority things (getting some of the translations into CVS, allowing students to post to the bboard bug). When these are done, the release will be cut.
As noted above, there are still bugs that Dee has identified for making dotlrn 2.0 upgradable for Sloan and I expect others will come along. We'll be continuing to fix these bugs and release point releases.
We also expect to be formallizing release (and other criteria) for future dotlrn release as the consortium builds.