[GNC-dev] Bugzilla Structure
Frank H. Ellenberger
frank.h.ellenberger at gmail.com
Tue Aug 28 12:21:09 EDT 2018
Am 28.08.2018 um 16:31 schrieb John Ralls:
>> On Aug 28, 2018, at 6:11 AM, Derek Atkins <warlord at mit.edu> wrote:
>> John Ralls <jralls at ceridwen.us> writes:
>>> One could, but I agree that a “General” component is better, so I’ve made one.
>>> I think David’s 777893 belongs in the T&CG, though, and he’s already
>>> moved it there.
>> Sure, having a General component makes sense if you don't know where it
>> should go, but I think it would be good to also use it for "umbrella"
>> bugs so that if there's a change that needs to be made in multiple
>> places we have a general bug and then doc-specific bugs.
>> At least that strcuted seems to make sense to me. Unless you feel it's
>> too much overhead?
>> We've used this structure before for major releases.
> Yes, that’s a reasonable use case. We just have to remember to close the umbrella bug when the individual ones are all closed.
> John Ralls
At least at bugzilla.gnome.org you got update notifications for bugs in
the blocks list if the status changed. I would assume it is the default
More information about the gnucash-devel