<p dir="ltr">See how gcc project manages it. May be that is sufficient for us too</p>
<div class="gmail_quote">On Apr 19, 2016 9:41 AM, "Burton, Ross" <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 19 April 2016 at 03:17, Christopher Larson <span dir="ltr"><<a href="mailto:clarson@kergoth.com" target="_blank">clarson@kergoth.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div>There may be something better out there, and if we can find it, great, but I think separate issues is better than not addressing the issue at all, but only if the tooling is good enough to help reduce overhead on the part of the devs dealing with it. Issue tracker overhead gets pretty frustrating at times.</div></div></div>
</blockquote></div><br>There may be a way of dealing with this using flags. If we had a flag for each release then we could add a flag for each release which is impacted by the bug, and track when they're resolved by changing flag state.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>
</blockquote></div>