Add mitaka release milestone

[Henry Gessau]

We do this for every release.

Add a 'mitaka' tag to the end of the alembic contract and expand branches in neutron, neutron-fwaas, neutron-lbaas and neutron-vpnaas.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/288212
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9ba57b8c23bf08c08f89c8f49a5514e14454701a
Submitter: Jenkins
Branch: master

commit 9ba57b8c23bf08c08f89c8f49a5514e14454701a
Author: Henry Gessau <email address hidden>
Date: Thu Mar 3 20:30:54 2016 -0500

    Tag the alembic migration revisions for Mitaka

    Previously when we had one repo with one alembic branch we would
    create a milestone revision on that single branch. Now we have
    multiple repos and expand/contract branches for each repo. So
    now we tag the final revision on every branch when we make a
    milestone release.

    The database can be upgraded with the command:
      neutron-db-manage upgrade <milestone>
    where <milestone> is an alias for all the revisions for a
    milestone.

    Partial-Bug: #1552935

    Change-Id: I44456a8389b761bc9e0f35845b90671daddf3b59

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/288213
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=19fe781f8c4c355c91821796cf81673e54c7d146
Submitter: Jenkins
Branch: master

commit 19fe781f8c4c355c91821796cf81673e54c7d146
Author: Henry Gessau <email address hidden>
Date: Thu Mar 3 20:36:25 2016 -0500

    Tag the alembic migration revisions for Mitaka

    Previously when we had one repo with one alembic branch we would
    create a milestone revision on that single branch. Now we have
    multiple repos and expand/contract branches for each repo. So
    now we tag the final revision on every branch when we make a
    milestone release.

    The database can be upgraded with the command:
      neutron-db-manage upgrade <milestone>
    where <milestone> is an alias for all the revisions for a
    milestone.

    Partial-Bug: #1552935

    Change-Id: Id8b012dc3f187b5a4b7be73a69910fe35657a0f5

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/288215
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=97282700b732b4f9a0709cdc51989fb064ca4ceb
Submitter: Jenkins
Branch: master

commit 97282700b732b4f9a0709cdc51989fb064ca4ceb
Author: Henry Gessau <email address hidden>
Date: Thu Mar 3 20:37:26 2016 -0500

    Tag the alembic migration revisions for Mitaka

    Previously when we had one repo with one alembic branch we would
    create a milestone revision on that single branch. Now we have
    multiple repos and expand/contract branches for each repo. So
    now we tag the final revision on every branch when we make a
    milestone release.

    The database can be upgraded with the command:
      neutron-db-manage upgrade <milestone>
    where <milestone> is an alias for all the revisions for a
    milestone.

    Partial-Bug: #1552935

    Depends-On: I0e6fc31dfa062c689936b2fe982147335ad9dce3

    Change-Id: Ieb240fa0783537567f13f039e095762ab15d3e8c

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/288214
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=c4cd13d903c86e50c5c80fd14db7a4e164fb5f0c
Submitter: Jenkins
Branch: master

commit c4cd13d903c86e50c5c80fd14db7a4e164fb5f0c
Author: Henry Gessau <email address hidden>
Date: Thu Mar 3 20:36:59 2016 -0500

    Tag the alembic migration revisions for Mitaka

    Previously when we had one repo with one alembic branch we would
    create a milestone revision on that single branch. Now we have
    multiple repos and expand/contract branches for each repo. So
    now we tag the final revision on every branch when we make a
    milestone release.

    The database can be upgraded with the command:
      neutron-db-manage upgrade <milestone>
    where <milestone> is an alias for all the revisions for a
    milestone.

    Partial-Bug: #1552935

    Change-Id: I66961aeaa2eef586eae11ee4eb08f61ebb91e54b