Release(Cook)                                                    Release(Cook)



NNAAMMEE
       How to release a version of Cook

CCHHEECCKKLLIISSTT
       This document describes the steps involved in issuing a new release of
       Cook.  The level of detail is too much in some places, and too little
       in others.

VVeerriiffyy CCuurrrreenntt BBaasseelliinnee
       Take the archive/cook-2.21.tar.gz file from the current baseline.
       Unpack it an verify that it configures and builds on each of the HP/UX,
       SunOs, Solaris, OSF/1 and AIX flavors.  There are usually small
       niggling problems (some of them are such bad UNIX implementations).
       Fix the problems and try again.

CCuutt AA NNeeww VVeerrssiioonn
       The releases are _p_o_s_t_-_n_u_m_b_e_r_e_d so that you must end the current branch
       and start a new branch with the desired release number.  This allows
       you to cut bug-fix sub-branches with sensible numbers when you want to
       release a bug fix.

       +o Set the project to one level up, and do a develop end on the current
         branch.

       +o Review it (hopefully without finding anything wrong),

       +o and the integrate it you normally would.

       +o Create a new branch for the release, and a new change on that branch.

       +o Create the change file for the last release (etc/CHANGES.2.21), and
         the release notes file for next release (lib/en/readme/new.2.21.so).

       +o When you integrate, use the -MINIMum option so that the version
         number in the documentation is correct.  Do a full regression test.

       +o Set your default project to the new branch.

       Resume these instructions once the new branch has been updated by this
       change.  Then these instructions will have the new version number in
       them, and you will be able to cut-and-paste from the text file straight
       into the xterm session.

UUPPLLOOAADD TTOO TTHHEE AARRCCHHIIVVEESS
       There are two archives to upload to.

   UUppddaattee PPrriimmaarryy AArrcchhiivvee
       Transfer a copy to http://www.canb.auug.org.au/~millerp/ by FTP.  Login
       as millerp and change to the WWW/cook directory (this corresponds to
       the /~millerp/cook/ directory for WWW clients).

              % aaeeccdd --bbll aarrcchhiivvee
              % ffttpp ffttpp..ccaannbb..aauuuugg..oorrgg..aauu
              user: mmiilllleerrpp
              ftp> bbiinnaarryy
              ftp> ccdd WWWWWW//ccooookk
              ftp>

       Delete the old version of Cook, to keep the space to a minimum.

              ftp> pprroommpptt
              ftp> mmddeelleettee ccooookk**
              ftp>

       Transfer the new version

              ftp> mmppuutt ccooookk**
              ftp> qquuiitt
              %


   UUppddaattee LLiinnuuxx AArrcchhiivvee
       Transfer a copy to sunsite.unc.edu by FTP.

       First check ftp://sunsite.unc.edu/pub/Linux/HOW.TO.SUBMIT and
       ftp://sunsite.unc.edu/pub/Linux/LSM-TEMPLATE to see if anything has
       changed.

       Login as anonymous and change to the /incoming/Linux directory.  Use
       the following commands

              % aaeeccdd --bbll aarrcchhiivvee
              % ffttpp ssuunnssiittee..uunncc..eedduu
              user: aannoonnyymmoouuss
              ftp> ccdd //iinnccoommiinngg//LLiinnuuxx
              ftp> bbiinnaarryy
              ftp> pprroommpptt
              ftp> mmppuutt ccooookk--**
              ftp> qquuiitt
              %


       The incoming directory is scanned, and the files placed into the
       archive automatically.  There is no need to send email to the archive
       maintainer.

NNOOTTIIFFIICCAATTIIOONNSS
       A couple of mailing lists and newsgroups need to be notified.

   NNoottiiffyy MMaaiilliinngg LLiissttss
       Send a notification to the _c_o_o_k_-_u_s_e_r_s_@_c_a_n_b_._a_u_u_g_._o_r_g_._a_u and _a_e_g_i_s_-
       _u_s_e_r_s_@_c_a_n_b_._a_u_u_g_._o_r_g_._a_u lists.  It should look like this:

              To: aegis-users@canb.auug.org.au, cook-users@canb.auug.org.au
              Subject: Cook 2.21 - file construction tool
              Reply-To: Peter Miller <millerp@canb.auug.org.au>

              I am pleased to announce that Cook 2.21 is now available.

              The cook program is a tool for constructing files, and
              maintaining referential integrity between files.

              Cook is a replacement for the traditional _m_a_k_e(1) tool.
              However, it is necessary to convert makefiles into cookbooks
              using the _m_a_k_e_2_c_o_o_k utility included in the distribution.

              You are invited to visit
                         http://www.canb.auug.org.au/~millerp/cook/
              for a more complete description of what Cook is, and access to
              the download files.  New features and bug fixes are described in
              the cook-2.21.README file.

              If you are putting together a source-code distribution and
              planning to write a makefile, consider writing a cookbook
              instead.  Although Cook takes a day or two to learn, it is much
              more powerful and a bit more intuitive than the traditional
              _m_a_k_e(1) tool.  And Cook doesn't interpret tab differently to 8
              space characters!

              _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 NNeewwssggrroouuppss
       Send a notification to the newsgroups can also be notified by email,
       which tends to work best as not all newsgroups are sufficiently
       available elsewhere.  It should look like this:

              To: mail2news@replay.com
              Newsgroups: alt.sources.d, comp.software-eng,
                      comp.software.config-mgmt, comp.sources.d, gnu.announce
              Subject: Cook 2.21 - file construction tool
              Reply-To: Peter Miller <millerp@canb.auug.org.au>

              I am pleased to announce that Cook 2.21 is now available.

              The cook program is a tool for constructing files, and
              maintaining referential integrity between files.

              Cook is a replacement for the traditional _m_a_k_e(1) tool.
              However, it is necessary to convert makefiles into cookbooks
              using the _m_a_k_e_2_c_o_o_k utility included in the distribution.

              You are invited to visit
                         http://www.canb.auug.org.au/~millerp/cook/
              for a more complete description of what Cook is, and access to
              the download files.  New features and bug fixes are described in
              the cook-2.21.README file.

              If you are putting together a source-code distribution and
              planning to write a makefile, consider writing a cookbook
              instead.  Although Cook takes a day or two to learn, it is much
              more powerful and a bit more intuitive than the traditional
              _m_a_k_e(1) tool.  And Cook doesn't interpret tab differently to 8
              space characters!

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

   UUppddaattee MMaaiilliinngg LLiisstt IInnffoo
       Update the cook-users list info, by sending email

              To: majordomo@canb.auug.org.au

              newinfo cook-users _p_a_s_s_w_o_r_d

              _a_t_t_a_c_h _t_h_e _R_E_A_D_M_E _f_i_l_e _h_e_r_e


   NNoottiiffyy LLiinnuuxx AAnnnnoouunnccee
       Send a notification to the comp.os.linux.announce list.  It should look
       like this:

              To: linux-announce@news.ornl.gov
              Subject: Cook 2.21 - file construction tool
              Reply-To: Peter Miller <millerp@canb.auug.org.au>

              I am pleased to announce that Cook 2.21 is now available.

              The cook program is a tool for constructing files, and
              maintaining referential integrity between files.

              Cook is a replacement for the traditional _m_a_k_e(1) tool.
              However, it is necessary to convert makefiles into cookbooks
              using the _m_a_k_e_2_c_o_o_k utility included in the distribution.

              You are invited to visit
                         http://www.canb.auug.org.au/~millerp/cook/
              for a more complete description of what Cook is, and access to
              the download files.  New features and bug fixes are described in
              the cook-2.21.README file.

              If you are putting together a source-code distribution and
              planning to write a makefile, consider writing a cookbook
              instead.  Although Cook takes a day or two to learn, it is much
              more powerful and a bit more intuitive than the traditional
              _m_a_k_e(1) tool.  And Cook doesn't interpret tab differently to 8
              space characters!

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

   UUppddaattee SSllaasshh DDoott
       Go to http://www.freshmeat.net/ and update the info for Cook.

CCOOPPYYRRIIGGHHTT
       _c_o_o_k version 2.21
       Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
       1997, 1998, 1999, 2000, 2001, 2002 Peter Miller; All rights reserved.

       The _c_o_o_k program comes with ABSOLUTELY NO WARRANTY; for details use the
       '_c_o_o_k _-_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 '_c_o_o_k _-_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                        Cook                        Release(Cook)
