Release(Aegis)                                                  Release(Aegis)



NNAAMMEE
        How to release a version of Aegis

CCHHEECCKKLLIISSTT
        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.

NNEEWW BBRRAANNCCHH
        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

                % aaeeddee --pp aaeeggiiss..5511 1199
                % aaeerrppaassss --pp aaeeggiiss..5511 1199
                % aaeeiibb --pp aaeeggiiss..5511 1199
                % aaeedd --pp aaeeggiiss..5511 1199
                % aaeebb --pp aaeeggiiss..5511 1199
                % aaeett --pp aaeeggiiss..5511 1199
                % aaeett --rreegg --pp aaeeggiiss..5511 --cc 1199
                % aaeeiippaassss --rreegg --pp aaeeggiiss..5511 --cc 1199
                %

        At this point, branch 19 if project _a_e_g_i_s_._5_1 is completed.  Cut a new
        branch, as follows

                % aaeennbbrr --pp aaeeggiiss..5511 2200
                %%

        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.

   VVeerriiffyy NNeeww BBrraanncchh
        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:

                % aaeennff eettcc//CCHHAANNGGEESS..5511..1199
                % bl*/etc/CHANGES.sh aegis.51.19 > etc/CHANGES.51.19
                %%


   VVeerriiffyy NNeeww BBrraanncchh
        The first pass of verifying the release set is to use the

                % aaeebb cchheecckk--ttaarrbbaallll
                _l_o_t_s _o_f _o_u_t_p_u_t
                %

        command.  This builds The tarball, and then unpacks it and builds
        Aegis from scratch.  It is a fairly vigorous test of the build and
        install, though highly Linux specific.  Fix any problems encountered.

        Take the archive/aegis.4.24.tar.gz file from the current change.  Try
        it out on as many different architectures as you have access to.  Try
        as many of these as you have access to: various Linux distributions
        (including AMD64), various BSD distributions, various Solaris
        versions, MacOSX, AIX, HP/UX, SGI.  Some are such bad implementations
        of Unix that you will almost always find something.

        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.

AARRCCHHIIVVEESS
        Once a viable release is ready, it is necessary to upload it to the
        archives.

   UUppddaattee PPrriimmaarryy AArrcchhiivvee
        The _a_e_b _c_h_e_c_k_-_t_a_r_b_a_l_l step, above, produces a bunch of files suitable
        for installation on SourceForge to as the CGI interface.  This serves
        a s a demo of Aegis' distributed development facilities, and is also
        used by Aegis developers for just this use.  Upload the _a_e_g_i_s_-_s_f_._t_g_z
        file and unpack it

                % ssccpp aaeeggiiss--ssff..ttggzz aaeeggiiss..ssoouurrcceeffoorrggee..nneett::..
                % sssshh aaeeggiiss..ssoouurrcceeffoorrggee..nneett
                _b_l_a_h _b_l_a_h
                %


        Transfer a copy to aegis.sourceforge.net by FTP.  Use the following
        commands

                % aaeeccdd --bbll aarrcchhiivvee
                % ssccpp --rr .. aaeeggiiss..ssoouurrcceeffoorrggee..nneett::aaeeggiiss..wweebb//hhttddooccss//..
                %


        You also need to update the SourceForge download servers.  This is
        best done by using FTP from _a_e_g_i_s_._s_o_u_r_c_e_f_o_r_g_e_._n_e_t to
        _u_p_l_o_a_d_._s_o_u_r_c_e_f_o_r_g_e_._n_e_t as this is a fast internal SourceForge network
        transfer, and not a slower through-the-cloud transfer.

   UUppddaattee SSoouurrcceeFFoorrggee AArrcchhiivvee
        Transfer a copy to upload.sourceforge.net by FTP.  Login as anonymous
        and change to the /incoming directory.  Use the following commands

                % aaeeccdd --bbll aarrcchhiivvee
                % ftp upload.sourceforge.net
                user: aannoonnyymmoouuss
                ftp> ccdd //iinnccoommiinngg
                ftp> bbiinnaarryy
                ftp> ppuutt aaeeggiiss--44..2244..ttaarr..ggzz
                ftp> ppuutt aaeeggiiss--44..2244..rrmm..ppddff
                ftp> ppuutt aaeeggiiss--44..2244..uugg..ppddff
                ftp> qquuiitt
                %


NNOOTTIIFFIICCAATTIIOONN
        Once the archives are ready, you can let folks know it's there.

        Only send the notifications _a_f_t_e_r the files are actually available at
        the archive site.

   SSoouurrcceeFFoorrggee..NNeett
        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 AAddmmiinn link, and
        the FFiillee RReelleeaasseess link, and the [[AAdddd RReelleeaassee]] 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.

   TTrraannssllaattiioonn PPrroojjeecctt
        Send a notification to the Translation Project
        _r_o_b_o_t_@_t_r_a_n_s_l_a_t_i_o_n_p_r_o_j_e_c_t_._o_r_g list.  It should look like this:

                To: robot@translationproject.org
                Reply-To: millerp@canb.auug.org.au
                Subject: aegis-4.24.pot

                I am pleased to announce that Aegis 4.24 is now available.
                The tarball may be found at
                http://aegis.sourceforge.net/aegis-4.24.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.

   NNoottiiffyy MMaaiilliinngg LLiisstt
        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.24 - a project change supervisor

                I am pleased to announce that Aegis 4.24 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.

   NNoottiiffyy WWeebb
        +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 chris@absolutegiganten.org that a new release of Aegis is
        available, he's the Debian package maintainer.

CCOOPPYYRRIIGGHHTT
        aegis version 4.24.D001
        Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
        2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Peter Miller

        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.

AAUUTTHHOORR
        Peter Miller   E-Mail:   millerp@canb.auug.org.au
        /\/\*             WWW:   http://www.canb.auug.org.au/~millerp/



Release Notes                        Aegis                      Release(Aegis)
