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)

Reply via email to