Aegis 3.10

• Aegis is designed around incremental development. It records these increments and file change sets, and can reproduce any historical increment.
• 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.
• Aegis has strong support for geographically distributed development. It supports both push and pull models, and many distribution topologies. Aegis' normal development process is used to validate received change sets before committing them.
• Aegis supports long transactions, also known as branches. 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.
• 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. (So far, only English is provided. Translations welcome.)
• 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 automaticly 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.

Year 2000 Status

• Aegis stores dates internally in Unix style (i.e. seconds offset), so internal storage of times and dates does not suffer from any Y2K problems.
• Aegis always uses the ANSI C standard strftime function to display times and dates. (This assumes that your vendor has supplied a compliant strftime.) This means that displaying dates does not assume fixed field widths, nor will it display the year 2000 as ``100''.
• When a user enters dates, they may specify years with an explicit century. If a user enters a year with an implicit century, the closest is assumed.

Files for Download

Aegis is also available from the Linux archives in the devel/vc directory.

Aegis and Windows NT

Compounding this is the fact that many sites want to develop their software for both Unix and Windows NT simultaneously. This means that the security of the repository needs to be guaranteed to be handled in the same way by both operating systems, otherwise one can act as a ``back door'' into the repository. Many sites do not have the same users and permissions (sourced from the same network register of users) on both Unix and Windows NT, making the mapping almost impossible even if the security models did actually correspond.

Most sites using Aegis and Windows NT together do so by running Aegis on the Unix systems, but building and testing on the NT systems. The work areas and repository are accessed via Samba or NFS.

There is more Software by Peter Miller at his home page.