The Tacker team is dependent on tosca-parser and heat-translator but they are not the only consumers.

I agree the structure is odd, and Sahdev has more of the history than I do.

In the past the requests from the Tacker team have come to Sahdev/me and we have created releases as needed.  For some reason this time a request went to the Heat ML, in addition to
a separate request to me directly.

I'm open to changes in the structure but I don't think Tacker is the right place to put the
deliverables.

Bob

On 6/20/2018 11:31 AM, Rico Lin wrote:
To continue the discussion in http://lists.openstack.org/pipermail/openstack-dev/2018-June/131681.html

Add Tacker and heat-translator to make sure all aware this discussion

On Thu, Jun 21, 2018 at 12:28 AM Doug Hellmann <d...@doughellmann.com <mailto:d...@doughellmann.com>> wrote:

    Excerpts from Zane Bitter's message of 2018-06-20 12:07:49 -0400:
    > On 20/06/18 11:40, Rico Lin wrote:
    > > I send a release patch now
    https://review.openstack.org/#/c/576895/
    > > Also, add Bob Haddleton to this ML who is considering as PTL for
    > > heat-translator team
    >
    > Is it time to consider moving the heat-translator and
    tosca-parser repos
    > from being deliverables of Heat to deliverables of Tacker? The
    current
    > weird structure dates from the days of the experiment with
    OpenStack
    > 'Programs' (vs. Projects).
    >
    > Heat cores don't really have time to be engaging with
    heat-translator,
    > and Tacker is clearly the major user and the thing that keeps
    getting
    > blocked on needing patches merged and releases made.

    It sounds like it. I had no idea there was any reason to look to
    anyone
    other than the Heat PTL or liaison for approval of that release. A WIP
    on the patch would have been OK, too, but if the Tacker team is really
    the one responsible we should update the repo governance.

    Doug

    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe:
    openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- May The Force of OpenStack Be With You,
    */Rico Lin
    /*irc: ricolin





<<attachment: bob_haddleton.vcf>>

__________________________________________________________________________
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

Reply via email to