VERSION is no longer set in configure because it's too hard to

propagate version string changes to the public (you have to
autoreconf, then reconfigure and reinstall).

Now, VERSION is set directory in Defaults.py.in and the Release.py
script updates that file directly.  Now we just need to run
./config.status and do a re-install.  I hope this will make things
easier.

I'm also bumping the version to 1.0b8, so I can do a release tomorrow.

2 files changed, 12 insertions, 5 deletions

diff --git a/admin/www/index.html b/admin/www/index.html
index 3b77606eb..fd75d2473 100644
--- a/admin/www/index.html
+++ b/admin/www/index.html
@@ -52,8 +52,8 @@ Before you can run Mailman, you need to download and install the
 
 <p>The first GNU release is not out yet.  For now, you can get the last
 pre-GNU beta release
-(<!-VERSION--->1.0b7<!-VERSION--->,
-released <!-DATE--->Dec 31 1998<!-DATE--->)
+(<!-VERSION--->1.0b8<!-VERSION--->,
+released <!-DATE--->Jan 14 1999<!-DATE--->)
 <A HREF="ftp://list.org/pub/mailman/">here</a>.
 </td>
 </tr>
diff --git a/admin/www/todo.html b/admin/www/todo.html
index 124cbe4f4..97b7c8674 100644
--- a/admin/www/todo.html
+++ b/admin/www/todo.html
@@ -47,19 +47,23 @@
 <LI> A web UI to the -urgent address.</LI>
 <LI> Better options for the policy on bundling digests (periodic w/ arbitrary   periods, size based, a combo of the two, etc).</LI>
 <LI> A button that will bundle a digest right now (tm).</LI>
+<LI> Ability to set the next digest volume and issue number from the Web</LI>
 <LI> A generic error template page.</LI>
 <LI> An option for setting the precedence header.</LI>
 <LI> Make the MM-tags accept useful options where appropriate.</LI>
 <LI> Revamp the admindb user interface, it's fairly clunky (include a decent   cataloging mechanism based on the file system).</LI>
 <LI> Be able to edit ALL the web pages, as well as the mail messages.</LI>
-<LI> Use templates from the templates dir until the list owner changes    the page, so the site admin can change them...</LI>
+<LI> Use templates from the templates dir until the list owner changes  the page, so the site admin can change them...</LI>
+<LI> All the list-admin to require approvals for unsubs</LI>
+<LI> Allow the admin to disable option settings by users</LI>
 </UL>
 <A NAME=c5><H3>List Member UI</H3>
 <UL>
 <LI> Editing your user options should put you back to the edit-options page. </LI>
 <LI> Allow the user to be excluded from postings if they're getting them  in the to: or cc: headers.</LI>
-<LI> An option to change your email address.</LI>
+<LI> An option to change your email address.  Or what might be easier:  allow a user to clone the options of an existing user into a new  address.</LI>
 <LI> Allow users to specify a different address for password reminders  (w/ confirmation), or come up w/ a better strategy for remailing lists  (could be done as the default, given a generic filter mechanism).</LI>
+<LI> Allow the user to get BOTH normal and digested delivery (but I still  don't understand why someone would want this)</LI>
 </UL>
 <A NAME=c6><H3>Site Administrator's UI</H3>
 <UL>
@@ -76,6 +80,7 @@
 <A NAME=c8><H3>Mailcmd interface</H3>
 <UL>
 <LI> Provide an email interface to administrative commands.</LI>
+<LI> Allow email unsubs from matching address to unsubscribe, possibly  adding an "allow open unsubscribes" option to control this.  Also,  adding a confirmation with hit-reply to resubscribe.</LI>
 </UL>
 <A NAME=c9><H3>Portability concerns</H3>
 <UL>
@@ -96,6 +101,8 @@
 <LI> Provide downloadable tar.gz's of the html archives</LI>
 <LI> sort by date should go most-recent to oldest</LI>
 <LI> allow list owner to edit archive messages</LI>
+<LI> support for alternative archiving systems, e.g. MHonArc, Hypermail</LI>
+<LI> archive link should do *something* reasonable before the first  message has been posted to the list.</LI>
 </UL>
 <A NAME=c12><H3>Code cleanup</H3>
 <UL>
@@ -114,6 +121,6 @@
 <LI> The threaded server should be able to off its workload to friendly machines   if it is overworked (distributed support).</LI>
 <LI> Refine locking to lock only necessary sections to get rid of superfluous  contention.</LI>
 <LI> Implement member profiles, using a class to store name,  organization, description, etc, and default option settings.  The  lists still can have their own data, but the user can set defaults in  their profile...</LI>
-<LI> Need to go through and verify there are no obvious security problems.</LI>
+<LI> Need to go through and verify there are no obvious security problems. Local Variables: mode: indented-text indent-tabs-mode: nil End:</LI>
 </UL>
 </BODY></HTML>