


Release(Aegis)                                     Release(Aegis)


NNAAMMEE
       How to release a version of Aegis

CCHHEECCKKLLIISSTT
       This document describes the steps involved in issuing a
       new release of Aegis.  It is a simple procedure, but there
       is enough to do, and it happens sufficiently rarely, that
       it was worth writing down.

NNEEWW BBRRAANNCCHH
       The version stamping is _p_o_s_t-numbered.  You decide what
       major or minor version number you want as you are about to
       release, not when you start work.

       Finish development of the branch in the normal way.  For
       example, if you are working on project _a_e_g_i_s_._5_1_._1_9, then
       you would say

              % aaeeddee --pp aaeeggiiss..5511 1199
              % aaeerrppaassss --pp aaeeggiiss..5511 1199
              % aaeeiibb --pp aaeeggiiss..5511 1199
              % aaeedd --pp aaeeggiiss..5511 1199
              % aaeebb --pp aaeeggiiss..5511 1199
              % aaeett --pp aaeeggiiss..5511 1199
              % aaeett --rreegg --pp aaeeggiiss..5511 --cc 1199
              % aaeeiippaassss --rreegg --pp aaeeggiiss..5511 --cc 1199
              %

       At this point, branch 19 if project _a_e_g_i_s_._5_1 is completed.
       Cut a new branch, as follows

              % aaeennbbrr --pp aaeeggiiss..5511 2200
              %%

       The branch number will default.  This is OK unless you
       ever skipped a number - in which case it will back fill
       which is usually undesirable.

       At this point project _a_e_g_i_s_._5_1_._2_0 is ready for use.  If
       you want a major version number increment, the process is
       similar, however you must also terminate the _a_e_g_i_s_._5_1
       branch, and you may well want to create a branch on the
       branch, to get back to a two-number version scheme.

              aede -p aegis.51 19 _e_t _a_l_, _t_o _c_o_m_p_l_e_t_e
              aede -p aegis 51 _e_t _a_l_, _t_o _c_o_m_p_l_e_t_e
              aenbr -p aegis 52
              aenbr -p aegis 52 0

       The purpose of a _p_o_s_t-numbered branching scheme is that,
       at any point, you can cut a suitable bug-fix sub-branch.










   VVeerriiffyy NNeeww BBrraanncchh
       Create a new change on the branch you just created, and
       start development of it.

       Update any version numbering files, or create any special
       release notes files, _e_t_c, as required.  Much of this can
       be obtained from Aegis, but not all of it.

       Create a new change for the previous branch to preserve
       the change file of the just-released version.  Continuing
       the above example:

              % aaeennff eettcc//CCHHAANNGGEESS..5511..1199
              % bl*/etc/CHANGES.sh aegis.51.19 > etc/CHANGES.51.19
              %%


   VVeerriiffyy NNeeww BBrraanncchh
       The first pass of verifying the release set is to use the

              % aaeebb RRPPMM
              _l_o_t_s _o_f _o_u_t_p_u_t
              %

       command.  This builds a RedHat package manager file.  It
       is a fairly vigorous test of the build and install, though
       highly Linux specific.  Fix any problems encountered.

       Take the archive/aegis.3.28.tar.gz file from the current
       baseline.  Unpack it and verify that it configures and
       builds on one of the Solaris boxes.  There are usually
       small niggling problems, so fix them and try again.

       Then unpack it on some other computer which is in the
       architecture list in the project _c_o_n_f_i_g file.  Configure,
       build and test it on this machine.

       Find yet another type of UNIX box and try again.  AIX or
       Pyramid are always good torture tests, they are such bad
       UNIX implementations.

       Once you have fixed all of the problems, develop end and
       integrate the change as normal.  This creates the initial
       baseline for this branch; it will contain the appropriate
       version numbers for release.

AARRCCHHIIVVEESS
       Once a viable release is ready, it is necessary to upload
       it to the archives.

   UUppddaattee PPrriimmaarryy AArrcchhiivvee
       Transfer a copy to ftp.canb.auug.org.au by FTP.  Login as
       millerp and change to the WWW/aegis directory (this
       corresponds to the /~millerp/aegis/ directory for WWW
       clients).  Use the following commands











              % aaeeccdd --bbll aarrcchhiivvee
              % ftp ftp.canb.auug.org.au
              user: mmiilllleerrpp
              ftp> ccdd WWWWWW//aaeeggiiss
              ftp> bbiinnaarryy
              ftp> pprroommpptt
              ftp> mmddeell aaeeggiiss--**
              ftp> mmppuutt aaeeggiiss**
              ftp> qquuiitt
              %


   UUppddaattee LLiinnuuxx AArrcchhiivvee
       Transfer a copy to sunsite.unc.edu by FTP.  Login as
       anonymous and change to the incoming/Linux directory.  Use
       the following commands

              % aaeeccdd --bbll aarrcchhiivvee
              % ftp sunsite.unc.edu
              user: aannoonnyymmoouuss
              ftp> ccdd iinnccoommiinngg//LLiinnuuxx
              ftp> bbiinnaarryy
              ftp> pprroommpptt
              ftp> mmppuutt aaeeggiiss--**
              ftp> qquuiitt
              %


       There is no need to send email to _e_w_t_@_s_u_n_s_i_t_e_._u_n_c_._e_d_u, it
       will be archived automatically in a day or two (or
       fifteen).

NNOOTTIIFFIICCAATTIIOONN
       Once the archives are ready, you can let folks know its
       there.

   NNoottiiffyy MMaaiilliinngg LLiisstt
       Send a notification to the _a_e_g_i_s_-_u_s_e_r_s_@_c_a_n_b_._a_u_u_g_._o_r_g_._a_u
       list.  It should look like this:

              To: aegis-users@canb.auug.org.au
              Reply-To: millerp@canb.auug.org.au
              Subject: Aegis 3.28 - a project change supervisor

              I am pleased to announce that Aegis 3.28 is now
              available.

              Aegis is a transaction-based software configuration
              management system.  It 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.

              You are invited to visit
                  http://www.canb.auug.org.au/~millerp/aegis/
              for a more complete description of what Aegis is,
              and access to the download files.

              For information about what new features are
              available in this release, please see the README
              file available at the above site.

              _p_u_t _y_o_u_r .sig _f_i_l_e _h_e_r_e


       Only send this notification _a_f_t_e_r the files are actually
       available at the archive site.

   UUppddaattee MMaaiilliinngg LLiisstt IInnffoo
       Update the aegis-users list info, by sending email

              To: majordomo@canb.auug.org.au

              newinfo aegis-users _p_a_s_s_w_o_r_d

              attach the _R_E_A_D_M_E file here


   NNoottiiffyy NNeewwssggrroouuppss
       A variety of newsgroups are relevant to Aegis, so notify
       them that the release is available.

              To: mail2news@replay.com
              Subject: Aegis 3.28 - a project change supervisor
              Reply-To: millerp@canb.auug.org.au
              Followup-To: millerp@canb.auug.org.au
              Newsgroups: alt.sources.d, comp.sources.d,
                  comp.software-eng, comp.software.config-mgmt,
                  gnu.announce

              I am pleased to announce that Aegis 3.28 is now
              available.

              Aegis is a transaction-based software configuration
              management system.  It 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.

              You are invited to visit
                  http://www.canb.auug.org.au/~millerp/aegis/
              for a more complete description of what Aegis is,
              and access to the download files.

              For information about what new features are
              available in this release, please see the README
              file available at the above site.

              insert _._s_i_g file here

       Please note that the Newsgroups: line may not actually
       wrap, or have spaces around the commas.

   NNoottiiffyy LLiinnuuxx AAnnnnoouunnccee
       Send a notification to the _c_o_m_p_._o_s_._l_i_n_u_x_._a_n_n_o_u_n_c_e list.
       It should look like this:












              To: linux-announce@news.ornl.gov
              Reply-To: millerp@canb.auug.org.au
              Subject: Aegis 3.28 - a project change supervisor

              I am pleased to announce that Aegis 3.28 is now
              available.

              Aegis is a transaction-based software configuration
              management system.  It 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.

              You are invited to visit
                  http://www.canb.auug.org.au/~millerp/aegis/
              for a more complete description of what Aegis is,
              and access to the download files.

              For information about what new features are
              available in this release, please see the README
              file available at the above site.

              _p_u_t _y_o_u_r .sig _f_i_l_e _h_e_r_e


       Only send this notification _a_f_t_e_r the files are actually
       available at the archive site.

   NNoottiiffyy WWeebb
       +o) Notify www.freshmeat.net that a new release of Aegis is
       available.  Search for ``aegis'' as there is already an
       application record.

       +o Notify www.cmtoday.com that a new release of Aegis is
       available.

       +o Notify davis@lrtw.org that a new release of Aegis is
       available, he's the Debian package maintainer.

       +o Notify pr@32bitsonline.com that a new release of Aegis
       is available.

CCOOPPYYRRIIGGHHTT
       aegis version 3.28
       Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997,
       1998, 1999, 2000, 2001 Peter Miller; All rights reserved.

       The aegis program comes with ABSOLUTELY NO WARRANTY; for
       details use the '_a_e_g_i_s _-_V_E_R_S_i_o_n _L_i_c_e_n_s_e' command.  This is
       free software and you are welcome to redistribute it under
       certain conditions; for details use the '_a_e_g_i_s _-_V_E_R_S_i_o_n
       _L_i_c_e_n_s_e' command.

AAUUTTHHOORR
       Peter Miller   E-Mail:   millerp@canb.auug.org.au
       /\/\*             WWW:   http://www.canb.auug.org.au/~millerp/



Release Notes                 Aegis                             1



