1 Using Aegis for RT development
3 1. The main line of RT development will be under the control
4 of the Aegis change management system, as administered by
5 Best Practical Solutions, LLC
7 2. We will use aedist to generate change sets for each change
8 checked in to the main Aegis repository. These change sets will be
9 either distributed by a mailing list or made available via the web,
12 3. Remote developers using Aegis will send aedist output for
13 their changes to rt-patches@bestpractical.com for review and
16 4. The aedist output should be sent to rt-patches@bestpractical.com
17 after the change has completed its local aede, but before aerpass.
19 5. If the change is rejected, the developer can aedeu to reopen
20 the change and fix whatever problems caused the review to not pass.
22 6. A baseline snapshot (aedist -bl) of the main Aegis repository
23 will be generated at least daily and made available via http
24 to provide a central location for synchronizing remote Aegis
27 7. Changes to the main Aegis repository will also be propagated
28 automatically to the tracking CVS repository.
30 Using CVS for RT development
32 1. CVS is accessed via anonymous cvs with the following CVSROOT:
34 :pserver:anoncvs@cvs.fsck.com:/raid/cvsroot/rt-2-1
36 2. Remote developers using CVS will send patches (cvs -diff
37 output) to rt-patches@bestpractical.com for integration into the
38 main Aegis repository. This allows anonymous CVS access to be used
39 for RT development by developers who are unable to use Aegis.