On Tue, Aug 15, 2017 at 5:46 PM, Alex Schultz <aschu...@redhat.com> wrote: > Hey folks, > > I'm proposing that in order to track tech debt that we're adding in as > part of development that we create a way to track these items and not > approve them without a bug (and a reference to said bug). Please > take a moment to review the proposed policy and comment. I would like > to start this for the queens cycle.
I also think we should frequently review the status of these bugs. Maybe unofficially from time to time and officially during milestone-3 of each cycle. I like the proposal so far, thanks. > A real world example of where this would beneficial would be the > workaround we had for buggy ssh. This patch was merged 6 months ago > to work around an issue in ssh that was recently fixed. However we > would most likely never have remembered to revert this. It was only > because someone spotted it and mentioned it that it is being > reverted now. > > Thanks, > -Alex > >  https://review.openstack.org/#/c/494044/ >  > https://review.openstack.org/#/q/6e8e27488da31b3b282fe1ce5e07939b3fa11b2f,n,z >  Thanks pabelanger > > __________________________________________________________________________ > 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 -- Emilien Macchi __________________________________________________________________________ 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