With many work streams in progress concurrently these days we are coming across the problem of upgrade package
clashes and conflicts more and more.
The system of creating a new upgrade package is manual, there is no risk assessment and it relies on developer communications via email and irc.
It was on the wishlist from a year ago that the upgrade system would want some management tools to make the process more efficient and less risky.
It is becoming a higher priority now with the increased number of developers involved in upgrades.
Therefore I would propose that some time is spent on designing (and then implementing) a system for managing the creation, change and deployment of upgrade packages during the development cycle.
Such a system could:
control version numbers
assert correct physical creation of packages
maintain the integrity of packages
assess risks and create alerts