This is PARI/GP, version 2.0.1.ALPHA.

  The ALPHA status means that bugs might still be lurking around, that the
documentation might not be absolutely accurate, and that some features or
function names might change on short notice. Apart from that word of caution,
we believe this version is stable enough to warrant an immediate release.

  We think it is important for you and for us that you try this new version
and send us feedback, since we can then improve the BETA version (scheduled
in a few months) and finally the RELEASE version. As usual for bug reports,
try to make them easily reproducible. For platform-specific bugs, we can
easily test all kinds of Sun workstations (under SunOS or Solaris),
Intel-compatible PC under Linux or FreeBSD, DEC Alpha under OSF/1 or Linux
and Hewlett-Packard workstations. For other types of platforms, we will try
to do our best, but do not hope for too much. 

  To save us time and worries, this is a UNIX-only, source-code-only,
release. We will provide binaries for later, stabler, versions.

==========================================================================

  To get started, run TeX on the file INSTALL.tex and have a look at the dvi
(extracted verbatim from Appendix A of the user manual). If you are in a
hurry, look at INSTALL.QUICK (ascii file). But a lot of information is
missing there.

  Typing 'make doc' should typeset the PARI/GP user's manual, a tutorial and
reference card in directory doc. This won't work if Configure did not succeed
(you can then type 'make force' in the doc directory. But you should make a
bug report before that, in case somebody could solve your problem.)

  See the files NEW and COMPAT for new features and incompatible changes
respectively between 2.0 and older versions. See Changelog for (terse
description of) subsequent patches.

Afterwards, you're on your own...

==========================================================================

There are three mailing lists devoted to the PARI/GP package (run courtesy
of Dan Bernstein), and most feedback should be directed to those. They are:

- pari-announce: to announce major version changes. You can't write to this
one, but you should probably subscribe.

- pari-dev: for everything related to the development of PARI, including
suggestions, technical questions, bug reports or patch submissions.

- pari-users: for everything else.

To subscribe, send empty messages respectively to

   pari-announce-subscribe@list.cr.yp.to
   pari-users-subscribe@list.cr.yp.to
   pari-dev-subscribe@list.cr.yp.to
 
If you are not a member of any of those lists and don't want to become 
one, you can write to us at 

  pari@math.u-bordeaux.fr

At the very least, we will forward you mail to the lists above and correct
faulty behaviour, if necessary. But we cannot promise you will get an
individual answer.

  Thanks for your support, and have fun !!
