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.4.16.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 aegis.sourceforge.net by FTP.  Use the following
       commands

              % aaeeccdd --bbll aarrcchhiivvee
              % scp -r . aegis.sourceforge.net:aegis.web/htdocs/.
              %


   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 metalab.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 metalab.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_@_m_e_t_a_l_a_b_._u_n_c_._e_d_u, it will be
       archived automatically in a day or two (or fifteen).

   UUppddaattee SSoouurrcceeFFoorrggee AArrcchhiivvee
       Transfer a copy to upload.sourceforge.net by FTP.  Login as anonymous
       and change to the /incoming directory.  Use the following commands

              % aaeeccdd --bbll aarrcchhiivvee
              % ftp upload.sourceforge.net
              user: aannoonnyymmoouuss
              ftp> ccdd //iinnccoommiinngg
              ftp> bbiinnaarryy
              ftp> ppuutt aaeeggiiss--44..1166..ttaarr..ggzz
              ftp> qquuiitt
              %


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.

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

   SSoouurrcceeFFoorrggee..NNeett
       This is _w_a_y harder than any sane person expects.  Go to
       http://sourceforge.net and login then go to
       http://sourceforge.net/projects/aegis/ and click the AAddmmiinn link, and
       the FFiillee RReelleeaasseess link, and the [[AAdddd RReelleeaassee]] link (near the bottom of
       the page).  In the "_N_e_w _r_e_l_e_a_s_e _n_a_m_e" box put the version number, and
       click the "_C_r_e_a_t_e _T_h_i_s _R_e_l_e_a_s_e" button.  In the "_P_a_s_t_e _T_h_e _N_o_t_e_s _I_n"
       box type
              http://aegis.sourceforge.net/change_log.txt
       And then finish the rest of the rather cumbersome dialog gunk.

   TTrraannssllaattiioonn PPrroojjeecctt
       Send a notification to the Translation Project
       _t_r_a_n_s_l_a_t_i_o_n_@_i_r_o_._u_m_o_n_t_r_e_a_l_._c_a list.  It should look like this:

              To: translation@iro.umontreal.ca
              Reply-To: millerp@canb.auug.org.au
              Subject: aegis-4.16.pot

              I am pleased to announce that Aegis 4.16 is now available.
              The tarball may be found at
              http://aegis.sourceforge.net/aegis-4.16.tar.gz

       Note that this is read and processed by a robot, so don't worry about
       the human-friendly language of the other notifications.

       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 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_@_a_u_u_g_._o_r_g_._a_u list.  It should
       look like this:

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

              I am pleased to announce that Aegis 4.16 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://aegis.sourceforge.net/
              for a more complete description of what Aegis is, and access to
              the download files.

              If you are upgrading, please take the time to read the release
              notes, which may be found in the README file in the sources, or
              on the web site at
                        http://aegis.sourceforge.net/change_log.txt

              _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 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 4.16 - 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 4.16 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://aegis.sourceforge.net/
              for a more complete description of what Aegis is, and access to
              the download files.

              If you are upgrading, please take the time to read the release
              notes, which may be found in the README file in the sources, or
              on the web site at
                        http://aegis.sourceforge.net/change_log.txt

              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 4.16 - a project change supervisor

              I am pleased to announce that Aegis 4.16 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://aegis.sourceforge.net/
              for a more complete description of what Aegis is, and access to
              the download files.

              If you are upgrading, please take the time to read the release
              notes, which may be found in the README file in the sources, or
              on the web site at
                        http://aegis.sourceforge.net/change_log.txt

              _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 4.16
       Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
       2000, 2001, 2002, 2003, 2004 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                      Release(Aegis)
