Hi William, The changes look good. You've agreed to add a test for the case where Person.verbose_bugnotifications=False and Team.verbose_bugnotifications=True. There are a couple of stylistic changes I'd like you to make, otherwise this is ready to go once that test has been added. On Thu, Jul 23, 2009 at 03:00:39PM -0000, William Grant wrote: > Thanks Graham, I believe I've fixed all those issues. > > === modified file 'database/sampledata/current.sql' > --- database/sampledata/current.sql 2009-07-23 04:49:04 +0000 > +++ database/sampledata/current.sql 2009-07-23 14:49:39 +0000 > @@ -4687,7 +4687,7 @@ > [snip reversion of change] > > === modified file 'lib/lp/bugs/doc/bugnotification-sending.txt' > --- lib/lp/bugs/doc/bugnotification-sending.txt 2009-07-23 04:51:44 +0000 > +++ lib/lp/bugs/doc/bugnotification-sending.txt 2009-07-23 14:45:59 +0000 > @@ -1247,9 +1247,40 @@ > cases where the user doesn't save bug notifications, which can make > subsequent notifications seem somewhat obscure. > > +To demonstrate verbose notifications, we'll create a bug, and subscribe > +some very picky users to it. Verbose Person wants verbose emails, while > +Concise Person does not. We'll also create a team with a member that > +wants verbose notifications. > + > + >>> switch_db_to_launchpad() > + >>> bug = factory.makeBug(product=factory.makeProduct(title='Foo'), > + ... title='Foo is broken', description='desc') We prefer to do wrapping of method calls thus: >>> bug = factory.makeBug( ... product=factory.makeProduct(title='Foo'), title='Foo is broken', ... description='desc') See http://dev.launchpad.net/PythonStyleGuide for details. The way you've done it is okay, but we've pretty much standardised on the style above, so we should stick with that (in fact I don't know why the other version is in the style guide any more; this one is the one that gets used). > + > + >>> vperson = factory.makePerson(displayname='Verbose Person', > + ...