    				Ken'ichi Fukamachi

    0.1	Helper tool to upgrade fml 2.x to fml 3.0
    0.2	Caution to automatic registration
    0.3	Changes from 2.2.1 to 3.0

    <>The difference between 2.2.1 and 3.0

    fml 3.0 provides new automatic registration.

      fml 3.0 "auto_subscribe" handler uses both actives and members.

    If you do not use automatic registration, you have nothing to do.

    0.1	Helper tool to upgrade fml 2.x to fml 3.0

       auto_regist -> auto_subscribe

    0.2	Caution to automatic registration

    How to handle member and actives files is different from fml 2.x to
    3.0. If you do not use automatic registration, you feel no difference.
    I recommend you use "auto_subscribe" handler but you can continue to
    use "auto_regist" in fml 2.x.

    Your choice follows

    	switch to use "auto_subscribe" handler (3.0)
    	continue to use "auto_regist" handler  (2.x)

    * 1. use "auto_subscribe" handler == move from 2.x to 3.0

    fml 3.0 automatic registration uses "auto_subscribe" handler
    irrespective of "auto_regist". When you use "auto_subscribe", you
    should copy members to actives before you change "auto_regist" to
    "auto_subscribe".

    Firstly copy members to actives. You have only to do this.

    	% cp members actives

    * 2. You can continue to use "auto_regist" in fml 3.0 too.
       You have nothing to do in this case.

    Caution: but I do not recommend case 2 since your policy will change.

    0.3	Changes from 2.2.1 to 3.0

    * automatic subscribe handles both members and actives.
      It is correct design but not compatible with past fml release.

    $Id: UPGRADE-3.0.wix,v 1.9 2000/12/03 07:15:01 fukachan Exp $