See how gcc project manages it. May be that is sufficient for us too On Apr 19, 2016 9:41 AM, "Burton, Ross" <[email protected]> wrote:
> > On 19 April 2016 at 03:17, Christopher Larson <[email protected]> wrote: > >> 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. >> > > 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. > > Ross >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
