Me and Paulo have just came back from HotSWUp'08, the first ACM workshop on hot topics on software upgrades. There we have presented a paper about co-authored by we two and Roberto. (Remember that, more generally, you can find a good deal of Mancoosi-related papers in the papers section of the main Mancoosi website.)
The (position) paper was about generalities in package upgrades (and their frequent failures!) as experienced in package-based FOSS distributions; interestingly enough, such details have not been properly presented thus far to the interested scientific communities. We believe our work contributed in closing the gap! In addition to the characterization, we point out some problems in state of the art counter measure to upgrade failures. Of course we also hint at the research directions Mancoosi is pursuing to have better upgrade support in future package managers.
The workshop was a pleasant experience and it was very well organized (which is not to be taken for granted in first editions of workshops...); kudos to the organizers for that. Nevertheless, I wasn't expecting to see that there are two big threads in the research community about software upgrades. On one hand there are people working on upgrades in the Mancoosi sense (i.e., how to deploy software on user machines, exploiting the abstraction of packages). On the other there is a huge amount of work on how to upgrade live systems, e.g., how to upgrade the code of a network service, without shutting down the service.
Of course the ideal target is having both safe software deployments and live software upgrades, we simply aren't there yet ...
In the meantime Mancoosi will do its best to address the first part of the issue!