Hi all, Glance was hoping to include our Community Images feature work in Ocata-1, but we have had some 11th hour communications about how migrations will look to and affect end users and operators. For now, we're not going to include that feature, but it raised a discussion during our meeting today.
Some of our team members are under the impression that if we merge a migration in Ocata-1, we can't then modify that migration in Ocata-2 or Ocata-3. We all agree that once 14.0.0 would be tagged and released, we couldn't touch that migration script, but there is no agreement about modifications between beta releases. Does the release team have or TC guidelines about this? A search hasn't turned up any documentation about this. On the other hand, I did find http://docs.openstack.org/project-team-guide/ptl.html?highlight=migration#at-the-beginning-of-a-new-cycle which seems to allow for squashing a previous cycle's migrations at the start of a cycle. Help and opinions are appreciated, -- Ian Cordasco Glance Release Liaison __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev