Re: [openstack-dev] [tc][goals] tracking status of old goals for new projects

Doug Hellmann wrote: There is a patch to update the Python 3.5 goal for Kolla [1]. While I'm glad to see the work happening, the change adds a new deliverable to an old goal, and it isn’t clear whether we want to use that approach for tracking goal work indefinitely. I see a few options. 1. We

Re: [openstack-dev] [tc][goals] tracking status of old goals for new projects

Excerpts from Jeremy Stanley's message of 2018-05-07 14:06:35 +: > On 2018-05-07 09:52:16 -0400 (-0400), Doug Hellmann wrote: > [...] > > 3. We could do nothing to record the work related to the goal. > [...] > > For situations like 557863 I think I'd prefer either the status quo > (the kolla

Re: [openstack-dev] [tc][goals] tracking status of old goals for new projects

On Mon, May 7, 2018 at 9:52 AM, Doug Hellmann wrote: > There is a patch to update the Python 3.5 goal for Kolla [1]. While > I'm glad to see the work happening, the change adds a new deliverable > to an old goal, and it isn’t clear whether we want to use that > approach for

Re: [openstack-dev] [tc][goals] tracking status of old goals for new projects

On 2018-05-07 09:52:16 -0400 (-0400), Doug Hellmann wrote: [...] > 3. We could do nothing to record the work related to the goal. [...] For situations like 557863 I think I'd prefer either the status quo (the kolla deliverable _was_ already listed so it could make sense to update it in that

[openstack-dev] [tc][goals] tracking status of old goals for new projects

There is a patch to update the Python 3.5 goal for Kolla [1]. While I'm glad to see the work happening, the change adds a new deliverable to an old goal, and it isn’t clear whether we want to use that approach for tracking goal work indefinitely. I see a few options. 1. We could update the