Re: Handling BUGS.

[Rob Browning]

Neil Jerram <address@hidden> writes:

> All sounds good to me, but how do we indicate that a bug has been
> fixed in one tree but not in another?

Just change it's "affects:" field.  i.e. you could have

  affects: 1.4 1.6 1.7

and when it's fixed in 1.6, just delete it from the line.  The only
time a bug would move to resolved is if it's been fixed in *all*
trees.  In this first, fairly simplistic approach, I mostly just
figured resolved as a place old bugs go to die to at least *somewhat*
reduce the inevitable clutter we'll have in active.  In the long term,
pumping this stuff into postgres via guile-pg or similar may be the
way to go, but that's a problem for our future selves :>

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD