My plea is for the developers to think about how their changes are
going to affect production deployments when upgrade time comes.
I for one would like to see the "ops" bug tag used more to try and track
these issues. If an upgrade makes something harder for operations
people, developers at the very least should create an ops bug to fix
that so that its at least tracked.
This seems like a good plan for a couple reasons: it tracks them, and
even if they aren't fixed before a release, it allows us to inform
people of possible complications during the upgrade.
This still requires people to think about how their changes may affect
ops, though.
- Ryan
14 messages in net.launchpad.lists.openstackRe: [Openstack] A plea from an OpenSt...