- Aegis supports large
teams and large projects.
| - Each project is a separate repository, with
separately configurable policies.
|
- Aegis supports change
sets and atomic commits.
| - Aegis support a development process which
ensures that change sets wont stop the project
“working” when they are integrated into the project
baseline. Working includes requiring that change sets
build successfully, and (optionally) that they include and
pass tests. It can also support code reviews of change sets,
in a variety of styles.
|
- Aegis is designed around
incremental development. It records these increments as file
change sets, and can reproduce any historical increment.
|
- Aegis is designed for
repository security (availability, integrity and
confidentiality).
|
- 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.
|
- Aegis supports multiple
repositories.
|
- 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.
|
- Aegis supports multiple
simultaneous active branches.
|
- Aegis supports branching
to any depth.
|
- 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.
|
- Aegis now has users all
around the world.
|
- Aegis is actively being
maintained and enhanced.
|
- 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.
|
- 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.
|
- Aegis runs on almost any
flavor of UNIX. Self configuring using a script generated by GNU
Autoconf.
|
