aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASE-INSTRUCTIONS
blob: e40b2b57efe182088fc923b09cdf207b41e3e809 (plain)
1
2
3
4
5
6
7
8
9
10
To do a release:

1. Torture-test the code against the list of test sites usuing the
   torturetest script.

2. Check in all files to RCS with an appropriate release label.

3. Run "makerelease" is root.  Read the script to see what it generates.

4. Run "upload" as yourself.
*/
I maintain an open-source POP and IMAP client called fetchmail.  It is
widely used in the Linux and open-source community, and is probably
the single most popular remote-mail client in that world.  You can
find out more about this project at
<http://fetchmail.berlios.de/>.

In order to be able to do thorough regression testing before each release,
I collect test accounts on as many different kinds of POP3, IMAP, and
ODMR servers as possible.  Because fetchmail is strictly conformant to the 
remote-mail RFCs, many server developers have found fetchmail a useful
standards-conformance test.

I'm writing to request test accounts on your server.  I support all flavors 
of POP2, POP3, IMAP and ODMR with either plain-password, CRAM-MD5, NTLM, 
GSSAPI, or Kerberos authentication.  I also support SSL/TLS.

It would be very helpful if I could have a separate test account for
each protocol you support (that is, separate POP3, IMAP, and ODMR
accounts) so I can do automated regression testing without worrying
about mailbox race conditions.