On Sat, Feb 21, 2009 at 8:01 PM, Derek Atkins <warl...@mit.edu> wrote:
> hi, > > > Quoting Charles Day <ceda...@gmail.com>: > > Is there a meta-bug for 2.3/2.4 to block in Bugzilla to indicate that a >> particular bug (e.g. bug 426111) has been fixed in trunk, and can be >> marked >> as "fixed" once a 2.3 or 2.4 has been made? Or some other way to keep >> track >> of bugs I've fixed in trunk that will not be backported for 2.2? >> Cheers, >> Charles >> > > No, we dont have one.. Generally we don't do a catch-all until after > we branch. It's not there to keep track of fixed bugs, it's there to > keep > track of bugs yet-to-be backported. > > You can already find bugs fixed for 2.3.x by a simple bugzilla query. > So what's the proper thing to do for bugs like 426111, which was reported in version 2.0.5 but has just recently been fixed in trunk and is unlikely to be backported for 2.2? How do we remember to mark that bug "fixed" once we branch for 2.3 or 2.4? > > -derek > > > -- > Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory > Member, MIT Student Information Processing Board (SIPB) > URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH > warl...@mit.edu PGP key available > > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
