On 2016-07-27 14:18, Steven Hardy wrote: > On Wed, Jul 27, 2016 at 08:41:32AM -0300, Honza Pokorny wrote: > > Hello folks, > > > > As the tripleo-ui project is quickly maturing, it might be time to start > > versioning our code. As of now, the version is set to 0.0.1 and that > > hardly reflects the state of the project. > > > > What do you think? > > I would like to see it released as part of the coordinated tripleo release, > e.g tagged each milestone along with all other projects where we assert the > release:cycle-with-intermediary tag: > > https://github.com/openstack/governance/blob/master/reference/projects.yaml#L4448 > > Because tripleo-ui isn't yet fully integrated with TripleO (e.g packaging, > undercloud installation and CI testing), we've not tagged it in the last > two milestone releases, but perhaps we can for the n-3 release? > > https://review.openstack.org/#/c/324489/ > > https://review.openstack.org/#/c/340350/ > > When we do that, the versioning will align with all other TripleO > deliverables, solving the problem of the 0.0.1 version?
Yes, this sounds great. > > The steps to achieve this are: > > 1. Get per-commit builds of tripleo-ui working via delorean-current: > > https://trunk.rdoproject.org/centos7-master/current/ Patch for per-commit builds: https://review.openstack.org/#/c/343834/ > 2. Get the tripleo-ui package installed and configured as part of the > undercloud install (via puppet) - we might want to add a conditional to the > undercloud.conf so it's configurable (enabled by default?) > > https://github.com/openstack/instack-undercloud/blob/master/elements/puppet-stack-config/puppet-stack-config.pp > > 3. Get the remaining Mistral API pieces landed so it's fully functional > > 4. Implement some basic CI smoke tests to ensure the UI is at least > accessible. > > Does that sequence make sense, or have I missed something? This makes sense to me. > > 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 __________________________________________________________________________ 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