[Bug 700601] Gnucash Aliases

John Ralls jralls at ceridwen.us
Sat Jun 1 00:48:17 EDT 2013

On May 31, 2013, at 11:51 AM, Geert Janssens <janssens-geert at telenet.be> wrote:

> On Friday 31 May 2013 06:52:49 John Ralls wrote:
> > On May 31, 2013, at 1:19 AM, Geert Janssens <janssens-geert at telenet.be> wrote:
> > > I'll do it.
> > > 
> > > What do I do with the current default assignees ? Just delete them
> > > or move them to the default qa contact or default cc list ?
> > I'd move both default contact and default qa to default cc, but it
> > looks like you already just moved contact to cc, which works too.
> > 
> > Regards,
> > John Ralls
> I actually like the idea of setting both default assignee and qa contact to the dummy accounts and have set things up like that.
> That allows us to continue to take assignment on bugs we intend to work on and still have all subscribed users follow the bug (because the qa contact remains the dummy user).
> The next question is of course if we really want to keep people in the default cc list. This list can only be modified by GnuCash Developers. Isn't the whole idea that everyone now can choose for themselves which groups they like to follow ?
> That will take some manual action of each person that was currently receiving bug reports already.
> I have sent an announcement in a separate mail with a list of currently cc'd users and ask all to update their own bugzilla mail preferences.
> The end goal is to empty the cc lists eventually.

OK. I wonder how many of the email addresses will turn out to be dead. It's a worthwhile exercise regardless.

I does seem that the default cc list allows devs to tailor their bugmail a bit more finely: Someone might want to get
bugmail on a particular module instead of all of the modules that are assigned to alias, which would mean that the
CC lists wouldn't be empty. 

John Ralls

More information about the gnucash-devel mailing list