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

Jeremy Stanley fungi at yuggoth.org
Mon May 7 14:06:35 UTC 2018

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 document) or option #3 (the cycle for
that goal is already well in the past, and certainly adding new
deliverables like kolla-kubernetes to a past goal sets unrealistic
expectations for future goals regardless of where we track them).

I really do, though, think we should simply accept that these goals
don't always (or even usually?) reach 100% coverage and that at some
point we need to be able to consider better means of keeping track
of, e.g., which deliverables work on which Python versions. The
goals process is excellent for reaching critical mass on such
efforts, but should not be considered a source of long-term support
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180507/46f18aa1/attachment.sig>

More information about the OpenStack-dev mailing list