[3227] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Minutes of 2002-04-03 release team meeting

daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Apr 3 14:17:35 2002

Date: Wed, 3 Apr 2002 14:17:31 -0500
Message-Id: <200204031917.OAA09579@equal-rites.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: release-team@mit.edu

Attending: ghudson aurora zacheiss othomas wedc rbasch miki jweiss

1. Status for last month

We did our status report; it will be sent out separately by Bill.

2. Alpha release status

Linux and Solaris are just about ready for testing.

The IRIX build was stuck on an emacs problem for a couple of weeks; we
don't know yet how well the rest of the tree builds.

3. MUA issues

Our transition plan status:

  - We have a first cut at the dialog for the mail icon, but it's
    ugly when done with gdialog, so we'l have to write our own.
  - We have to write the pine front-end script.
  - We have to modify the pine configuration to list the "Old mail"
    folder collection.

We developed a concern about users who, having become accustomed to
the IMAP mail readers in 9.1, unwittingly log into a 9.0 machine and
(confusedly) use xmh to inc their mail into MH (which they will be
able to see as "Old mail" in the new clients, but they may not think
to try that).  We don't have a particularly satisfactory solution
right now.

A similar issue affects pine: a user of 9.1 could become accustomed to
running "pine" and then try running it on a 9.0 machine where there is
no pine in the release.  If they have the sipb locker added, they will
get the version of pine which immediately sucks their mail into pine
oblivion.  This issue is a little more tractable because the sipb
locker can be modified without people having to take updates.

It would be nice if Evolution had support for word documents as MIME
attachments.

4. Linux kernel 2.4.9-31 issue

(Background: Linux 2.4.9-31 doesn't boot on a very small number of
machines; see
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=61340.  So far our
only reports from the field are one DSpace machine.)

We discussed how to warn users about this problem, since it is very
rare and it's not clear how much assistance we can offer people if
they are affected.  Bill expressed willingness to do site visits to
take care of the people affected since we don't expect more than one
or two.  Bill will also send the announcement.

home help back first fref pref prev next nref lref last post