2004-04-22: Beta 0.90

  This release incorporates all features originally planned for RVM by the
  author, and concludes RVM's alpha development status.  An extensive beta
  testing phase will now begin where RVM will be used daily in a production
  environment.

  New features may be added as requested by the OpenSource community and as
  time for development allows.  As always patches for both feature requests
  and bug reports are welcomed by the author with open arms.


  Platforms tested:

  Platform                                 Config Compile Passes Tests
  ---------------------------------------- ------ ------- -----------------
  i386-unknown-freebsd4.10    FreeBSD-4.8  OK     OK      OK
  i386-unknown-netbsdelf1.6.1 NetBSD-1.6.1 OK     OK      OK
  i686-pc-linux-gnu           Debian-2.2   OK     OK      1 test fails [2]
  i686-pc-linux-gnu           RedHat-9.0   OK     OK      OK
  powerpc-apple-darwin6.8     OS-X-10.2    OK     OK      1 test fails [1]
  sparc-sun-solaris2.9        Solaris-9    OK     OK      OK
  x86_64-unknown-linux-gnu    SuSE-8-ES    OK     OK      1 test fails [2]


  [1]: test-rconfig-004 fails on Mac-OS-X-10.2
    This test uses a set of configuration files that intentionally loop,
    causing RVM to re-read the same files over and over again util memory is
    exhausted.  On this platform, when memory is exhausted, test-rconfig-004
    fails at (backtrace):

      1) _lookup_all_secure()
      2) lu_getpwname()
      3) getpw_internal()
      4) getpw()
      5) filestatus::path(std::string)

    This failure is not seen in OS-X-10.1.  To the best of the author's
    knowledge this is an emergent feature of 10.2 that is caused by either a
    lack of memory or a lack of stack space.

    No error is thrown by test-rconfig-004, it merely exits with a
    segmentation fault after receiving signal EXC_BAD_ACCESS (could not access
    memory error).  10.2 seems to ignore the try {...} block that wraps the
    code that causes this mess, meaning that if such a lack of resource occurs
    in real life RVM will be unable to recover from the error.
    
    To the best of the author's knowledge, so long as a user does not run out
    of memory or stack space then RVM should function as desired.
    
    The author seeks a solution.

  [2]: test-rvm fails
    This has been seen on SuSE-8-ES running on an AMD64 Opteron, and on
    Debian-2.2 running on an i686.

    Test-rvm fails an assertion at line 580: in.is_open().  Errno is not set
    when the failure occurs.  At this time the cause of failure is unknown.
    It is unknown whether or not RVM will function as desired on this
    platform.

    This behavior is not seen on Redhat-9.0 running on the same architecture
    as Debian-2.2.
    
    The author seeks a solution.
    

  To-do:

  - Comb through the code and make sure that all exceptions are being handled
    gracefully.  (*sigh*)

# vim:et:ts=2:shiftwidth=2
