Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!itivax!vax3!scs
From: scs@vax3.iti.org (Steve Simmons)
Newsgroups: comp.mail.uucp
Subject: Elm 2.2 release
Summary: Posting patches, posting full source
Message-ID: <911@itivax.iti.org>
Date: 2 Apr 89 21:51:27 GMT
Sender: news@itivax.iti.org
Reply-To: scs@vax3.iti.org (Steve Simmons)
Organization: Industrial Technology Institute
Lines: 28

In article <574@ispi.UUCP> jbayer@ispi.UUCP (Jonathan Bayer) writes:
>Use a good mail program such as Elm 2.2 (which is being released to the
>sources group today or tomorrow).  It hides all of the headers unless
>you want to see them.

This brings up an issue which other newsgroups may have already
dealt with -- distributing patches and source for high-popularity
programs.

Rich $, bless his little heart, has a boatload of things on schedule
to release.  Since the last Elm in comp.sources.unix was 1.5, it's
pretty reasonable to put 2.2 out thru him.  But what about 2.3?  2.4?
It becomes silly to post the full release every time.

Let's release Elm to c.s.u *at most* yearly, and then only if there
is a significant change from the previous postings.  By 'significant'
I mean the patches getting nearly as large as the source.

At the same time, let's make distribution to the present users as fast
as possible.  This means not only future upgrade releases.  I'd like to see
a 2.1->2.2 patch released to this group and crossposted to comp.source.d.

Oh yeah, one pet peeve.  I hope the release of 2.2 is a full "true"
one, not 2.1 plus patch.

   Steve Simmons         Just another midwestern boy
   scs@vax3.iti.org  -- or -- ...!sharkey!itivax!scs
         "Hey...you *can* get here from here!"