Bug Triage (was Re: scheduled transactions make bad transactions with 1.8.9 ?)

[Derek Atkins]

Right now we don't have a good process in place for marking bugs
as "reproducible".  We do use the NEEDINFO to mark a bug as,
well, need more info. :)

I suppose that, once you confirm a bug you can change it from UNCO ->
NEW to confirm it.

If you need bits I'm sure that Wilddev can help.

-derek

"Steve Romanow" <slestak at cavtel.net> writes:

> I would like to help as well.  How can we id bugs that are in need of this
> work?  Just entries with no reproduce info, or do you want verification of
> supplied reproduce info?
>
> Volker, we should mark them when we start so we dont duplicate effort.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>
>

-- 
       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
       warlord at MIT.EDU                        PGP key available