db-archiving spec missing developer impact

[Walt Boring]

The kilo db-archiving cinder spec currently has "None" for the developer impact. This is definitely not the case. When shadow tables are part of cinder, any developer making db changes also has to make shadow table changes.

We need to update the spec to talk about the scenarios of changes required for developers adding new tables, modifying existing tables and migrating data.

The spec in question:

https://github.com/openstack/cinder-specs/blob/master/specs/kilo/db-archiving.rst

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/160534

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/160534
Committed: https://git.openstack.org/cgit/openstack/cinder-specs/commit/?id=2be32b0c98aae31bf4a715177c44868999a37c4a
Submitter: Jenkins
Branch: master

commit 2be32b0c98aae31bf4a715177c44868999a37c4a
Author: Ivan Kolodyazhny <email address hidden>
Date: Tue Mar 3 00:17:18 2015 +0200

    Add 'Developer Impact' section for DB Archiving

    Specify developers actions for database migrations for shadow tables.

    Closes-Bug: #1427402
    Related blueprint: db-archiving

    Change-Id: I8d49ef3b10c11a917f897e8135670ffe35769748