Get rid of one_last_digest. Move this into a separate OneLastDigest table.

Make it explicit to get the last digest (I could imagine an user selecting not
to).  Actually add tests for this.

Start to get rid of 'from storm.locals import *' in favor of more specific
imports.  Start to use Store.of() instead of config.db.store where we can.

Rework (delivery)MemberRosters to use the Member attributes.  This ensures
that the layered lookup happens at the expense of query optimization.

Sundry and various cleanups.

2 files changed, 3 insertions, 2 deletions

diff --git a/src/mailman/docs/addresses.txt b/src/mailman/docs/addresses.txt
index 9eccb2673..a8ae24840 100644
--- a/src/mailman/docs/addresses.txt
+++ b/src/mailman/docs/addresses.txt
@@ -148,7 +148,8 @@ subscribed, a role is specified.
 
     >>> address_5 = usermgr.create_address(
     ...     u'eperson@example.com', u'Elly Person')
-    >>> mlist = config.db.list_manager.create(u'_xtext@example.com')
+    >>> mlist = create_list(u'_xtext@example.com')
+
     >>> from mailman.interfaces.member import MemberRole
     >>> address_5.subscribe(mlist, MemberRole.owner)
     <Member: Elly Person <eperson@example.com> on
diff --git a/src/mailman/docs/membership.txt b/src/mailman/docs/membership.txt
index 7f9f16738..65f5b37ed 100644
--- a/src/mailman/docs/membership.txt
+++ b/src/mailman/docs/membership.txt
@@ -2,7 +2,7 @@ List memberships
 ================
 
 Users represent people in Mailman.  Users control email addresses, and rosters
-are collectons of members.  A member gives an email address a role, such as
+are collections of members.  A member gives an email address a role, such as
 'member', 'administrator', or 'moderator'.  Roster sets are collections of
 rosters and a mailing list has a single roster set that contains all its
 members, regardless of that member's role.