head	1.2;
access;
symbols;
locks; strict;
comment	@# @;


1.2
date	2001.07.24.17.52.33;	author leonardr;	state Exp;
branches;
next	1.1;

1.1
date	2001.07.24.17.50.23;	author leonardr;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Corrected bad HTML.
@
text
@<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
 <title>Tigris Versions</title>
</head>

<body>

<h1>Tigris Versions</h1>

<p>Leonard Richardson &lt;leonardr at collab dot net&gt;<br>
July 24, 2001<br>
<small>$Id: versions.html,v 1.1 2001/07/24 17:50:23 leonardr Exp $</small>

<h2>Abstract</h2>

<p>An account of Tigris versions, past and present. Tags mentioned are
consistent across all the tools hosted in tigris.org repositories.

<h2>Tigris Classic</h2>

<p>The term "Tigris classic" is used to describe a large number of
slightly incompatible early versions of Tigris. It describes the
system as it was from January 2000 until December 2000, when Tigris
0.8.4 was released. The latest "Tigris classic" code is accessible
with the TIGRIS_BASELINE tag.

<h2>0.8.4-1.0.0</h2>

<p>These are old versions, each of which has a tag of the form
TIGRIS_[major]_[minor]_[revision].

<h2>Current and future versions: 1.0.x, 1.1.0, 1.2.0</h2>

<p>Versions <b>1.0.x</b> are bugfix releases created by tagging the
TIGRIS_1_0 branch. The 1.0.x stable branch will culminate in the
<b>1.1.0</b> release.

<p>The HEAD of the CVS tree, a development branch containing many new
features, is destined to become <b>1.2.0</b>. It will then be branched
as the stable TIGRIS_1_2 branch.

</body>
</html>
@


1.1
log
@Added a reckoning of Tigris versions, past and present.
@
text
@d13 1
a13 1
<small>$Id: direct_derived_roles.html,v 1.3 2001/06/22 00:06:56 leonardr Exp $</small>
d15 1
a15 1
<h2>Abstract</2>
@

