Release Early, Release Often
=========================================================================

Contents:
 * About
 * Documentation
 * Feedback
 * Licensing
 * Release Notes

				About
				=====

RERO is a tool that automates the release process of software that
appears to be stable. It can also be used to do static releases of
software.

In short, RERO uses a revision control system (like CVS) to build
software (like wsmake) and, according to some rules (like DejaGNU),
make a release (like 1.0.42) while submitting the release information
to an announcement site (like c.o.l.a.).

Given that, you should probably ask yourself if you really need to use
RERO. You may be able to use the system you have already if you want
complete control over when and how a release of your software happens.

	   You can simply release early and release often.

However, RERO is useful for people who want to make a release, based on
the current status of their software, with or without developer
intervention. In other words, RERO could make a release at anytime
(like when you are asleep), based on the apparant stability of your
software.  You as a developer would not need to worry as much about
release management and the demands of releasing often. RERO does its
best to figure that out.  All you would have to do is customize when
it is appropriate to release, and where to release it.

RERO is  also useful for people  like me who find  themselves stuck in
the cathedral all too often and  not wanting to spend time preparing a
very detailed and thorough minor release. It does some basic checks to
make  sure that  the software  works (to  the best  of  its knowledge)
before making a new release.

Development for RERO began on October 14, 2002. It has some lofty
goals:

  * Of course, implementing the "release early, release often"
    principle as described by Eric S. Raymond.

  * Strengthening the path from developer to customer. Release often,
    even if it means releasing while you sleep.

  * Having fun learning about release management automation by using
    the tool on itself.

			    Documentation
			    =============

The following locations provide documentation for using RERO:

  * In the `docs' directory of the source distribution.
  * At the website: http://rero.sourceforge.net/docs/

			       Feedback
			       ========

  * Mailing Lists
    http://sourceforge.net/mail/?group_id=72944

  * Bug Reports
    codeserf@users.sf.net

  * Contact Authors
    See the `AUTHORS' file in the source distribution.

			      Licensing
			      =========

For licensing instructions, read the file `COPYING' in the source
distribution.

			    Release Notes
			    =============

For release notes, read the file `NEWS' in the source distribution.

			  Build Requirements
			  ==================

RERO depends on Perl. In particular, versions greater than 5.8.0
should work fine. I have not been able to test older versions. It
strictly depends on the Getopt::Long and Time::HiRes modules.
  http://www.perl.org/

To use the graphing script you will need gnuplot:
  http://www.gnuplot.info/
  
Some systems for which I test and build on are:
  Debian GNU/Linux i386 (unstable)
  Debian GNU/Linux sparc (unstable)
  PS2 Linux ;-)

Instructions for building and installing RERO:
  $ ./configure
  $ make
  $ make check       # (optional)
  $ make install

It will map its files under /usr/local by default. To change that, use
the --prefix, or see the INSTALL file for more information.

-----------------------------------------------------------------------------
Website	      : http://rero.sourceforge.net/