Doug Hellmann wrote: > What makes reno a good fit for this task? It seems like updating a > regular documentation page in the source tree would work just as well, > since presumably these technical debt descriptions don't need to be > backported to stable branches.
Yeah it feels like reno would add complexity for little benefit in that process... Better track debt in a TODO document, or a proper task tracker ? -- 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