.\"
.\" aegis - project change supervisor
.\" Copyright (C) 1997-2001 Peter Miller;
.\" All rights reserved.
.\"
.\" This program is free software; you can redistribute it and/or modify
.\" it under the terms of the GNU General Public License as published by
.\" the Free Software Foundation; either version 2 of the License, or
.\" (at your option) any later version.
.\"
.\" This program is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public License
.\" along with this program; if not, write to the Free Software
.\" Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.
.\"
.\" MANIFEST: input for archive/aegis.html
.\"
.de an-p-footer
..
.ad l
.hy 0
.so version.so
-
Aegis supports large teams and large projects.
| -
Each project is a separate repository, with separately configurable
policies.
|
.br
-
Aegis supports change sets.
| -
Aegis enforces a development process which requires that change sets
``work'' before they may be integrated into the project baseline.
Works includes requiring that change sets build successfully, and
(optionally) that they include and pass tests. It also ensures
that code reviews have been performed.
|
.br
-
Aegis is designed around incremental development. It records these
increments as file change sets, and can reproduce any historical
increment.
|
.br
-
Aegis is designed for repository security
(availability, integrity and confidentiality).
|
.br
-
Aegis supports distributed repositories.
| -
Aegis supports both push and pull distribution models, and many
distribution topologies. Aegis' normal development process is used to
validate received transactions before accepting them.
|
.br
-
Aegis supports multiple repositories.
|
.br
-
Aegis supports multiple lines of development.
| -
Aegis supports long transactions, also known as ``branches'' or ``lines
of development''. This allows appropriately created changes to be
treated as if they were projects, and thus to have changes made to them.
This allows a hierarchy of changes within changes, to any desired depth.
|
.br
-
Aegis supports multiple simultaneous active branches.
|
.br
-
Aegis supports branching to any depth.
|
.br
-
Aegis is mature software - it was first released in 1991.
| -
The error messages of Aegis have been
internationalized. This means
that error messages can be in your native language, if a translation has
been provided.
More translations are welcome.
|
.br
-
Aegis now has users all around the world.
|
.br
-
Aegis is actively being maintained and enhanced.
|
.br
-
Aegis is easy to use.
It is big, it does have a lot of functionality,
but the essential process can be learned in less than a day.
| -
The Aegis development model is very versatile.
It is suitable for a huge range of projects and teams.
|
.br
-
There is a script-based reporting facility, allowing many custom reports
to be generated from the Aegis database. There are also many report
scripts distributed with Aegis.
| -
There is an intranet Web interface, which is installed automatically when
the install script discovers a web server. This interface allows browsing
of much of the Aegis meta-data, of all publicly accessible projects.
|
.br
-
Aegis runs on almost any flavor of UNIX.
Self configuring using a script generated by GNU Autoconf.
|
.br