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 could update the existing document.
2. We could set up stories in storyboard like we are doing for newer
goals.
3. We could do nothing to record the work related to the goal.
I like option 2, because it means we will be consistent with future
tracking data and we end up with fewer changes in the governance repo
(which was the reason for moving to storyboard in the first place).
What do others think?
I don't have a strong opinion, small preference for (2). At the end of
the cycle, the goal becomes just another story with leftover tasks.
--
Thierry Carrez (ttx)
__________________________________________________________________________
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