On Tue, Nov 8, 2016 at 6:38 PM, Steven Dake (stdake) <std...@cisco.com> wrote: > Hey folks, > > As we split out the repository per our unanimous vote several months ago, we > have a choice to make (I think, assuming we are given latitude of the > release team who is in the cc list) as to which version to call > kolla-ansible. > > My personal preference is to completely retag our newly split repo with all > old tags from kolla git revisions up to version 3.0.z. The main rationale I > can think of is kolla-ansible 1 = liberty, 2 = mitaka, 3 = newton. I think > calling kolla-ansible 1.0 = newton would be somewhat confusing, but we could > do that as well. > > The reason the repository needs to be retagged in either case is to generate > release artifacts (tarballs, pypi, etc). > > Would also like feedback from the release team on what they think is a best > practice here (we may be breaking new ground for the OpenStack release team, > maybe not – is there prior art here?) > > For a diagram (mostly for the release team) of the repository split check > out: > https://www.gliffy.com/go/share/sg9fc5eg9ktg9binvc89 > > Thanks! > -steve > > > __________________________________________________________________________ > 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 >
I would love to get inputs from release team, though one of the recent repo split I remember is neutron and if I look at the history, old tags from git revisions are preserved. I think we can follow the same process for kolla and kolla-ansible split. -coolsvap __________________________________________________________________________ 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
