Re: [openstack-dev] [reno] an alternative approach to known issues

2018-02-12 Thread Gabriele Cerami
On 09 Feb, Thierry Carrez wrote: > 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

Re: [openstack-dev] [reno] an alternative approach to known issues

2018-02-09 Thread Thierry Carrez
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

Re: [openstack-dev] [reno] an alternative approach to known issues

2018-02-09 Thread Doug Hellmann
Excerpts from Gabriele Cerami's message of 2018-02-08 22:43:56 +: > Hi, > > sometimes it happens, while reviewing a patch, to find an issue that > is not quite a bug, because it doesn't limit functionality, but > may represent a problem in some corner case, or with some possible > future

[openstack-dev] [reno] an alternative approach to known issues

2018-02-08 Thread Gabriele Cerami
Hi, sometimes it happens, while reviewing a patch, to find an issue that is not quite a bug, because it doesn't limit functionality, but may represent a problem in some corner case, or with some possible future modification in some component involved in the patch; it may best be described as a