Aegis 4.22 reviewDownload
Aegis is a transaction-based software configuration management system. Aegis project provides a framework within which a team of dev
Aegis is a transaction-based software configuration management system.
Aegis project provides a framework within which a team of developers may work on many changes to a program independently, and Aegis coordinates integrating these changes back into the master source of the program, with as little disruption as possible.
Here are some key features of "Aegis":
All operations on the repository are based on change sets.
True configurations. All changes are reproducable snapshots. Every change set has a unique configuration identifier.
Ability to rename files without losing their history.
Binary files are supported.
File meta-data are versioned. Aegis versions not only file contents and file existence, but also the `execute' permission flag on files and file attributes. Users can attach arbitrary meta-data ("attributes") to any file.
Commits are truly atomic. No part of a commit takes effect until the entire commit has succeeded. Log messages are attached to the revision, not stored redundantly as in CVS.
Access controls on lines of development (branches). Creating a branch in Aegis can be accomplished with a single, fast command.
Repository synchronization, geographically distributed development.
Optimal performance for all users, local or remote, beuase there isn't any difference. Repository syncgronization means all developers, local or remote, get optimal performance.
Disconnected commits. Have you ever screwed up a code base on an airplane or a vacation and wished you could back out? Productivity while traveling, at home, at remote offices with partial or slow network connectivity.
Peer-to-peer architecture. Work may flow in any direction, including "sideways" between two sites without involving a master site.
Costs are proportional to change size, not data size. In general, the time required for an Aegis operation is proportional to the size of the changes resulting from that operation, not to the absolute size of the project in which the changes are taking place.
Aegis uses a collection of very simple on- disk formats for archives and ancillary databases. It does not require or use a relational database, hash-table database, or anything else that requires acolytes and administrators. Consequently, creating a new project repository is utterly trivial: a single Aegis command does it, basically by creating some new directories
What's New in This Release:
There is a new aefinish(1) command which may be used to automatically finish development of a change set.
There is a new aetar -exclude-auto-tools option, which can be used to exclude common GNU Autoconf and Automake files.
There is a new aede-policy(1) command for checking change sets before they end development.
There is a new ae-repo-ci(1) command which may be used for parallel check-in into CVS or SVN.
Many more minor feature enhancements were done.
Many bugs were fixed.
Aegis 4.22 keywords