Release(Cook)                                                    Release(Cook)



[1mNAME[0m
        How to release a version of Cook

[1mCHECKLIST[0m
        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.

[1mVerify Current Baseline[0m
        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.

[1mCut A New Version[0m
        The releases are [4mpost-numbered[24m 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.

[1mUPLOAD TO THE ARCHIVES[0m
        There are two archives to upload to.

   [1mUpdate Primary Archive[0m
        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).

                % [1maecd -bl archive[0m
                % [1mftp ftp.canb.auug.org.au[0m
                user: [1mmillerp[0m
                ftp> [1mbinary[0m
                ftp> [1mcd WWW/cook[0m
                ftp>

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

                ftp> [1mprompt[0m
                ftp> [1mmdelete cook*[0m
                ftp>

        Transfer the new version

                ftp> [1mmput cook*[0m
                ftp> [1mquit[0m
                %


   [1mUpdate Linux Archive[0m
        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

                % [1maecd -bl archive[0m
                % [1mftp sunsite.unc.edu[0m
                user: [1manonymous[0m
                ftp> [1mcd /incoming/Linux[0m
                ftp> [1mbinary[0m
                ftp> [1mprompt[0m
                ftp> [1mmput cook-*[0m
                ftp> [1mquit[0m
                %


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

[1mNOTIFICATIONS[0m
        A couple of mailing lists and newsgroups need to be notified.

   [1mNotify Mailing Lists[0m
        Send a notification to the [4mcook-users@canb.auug.org.au[24m and [4maegis-[0m
        [4musers@canb.auug.org.au[24m 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 [4mmake[24m(1) tool.
                However, it is necessary to convert makefiles into cookbooks
                using the [4mmake2cook[24m 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 [4mmake[24m(1) tool.  And Cook doesn't interpret tab
                differently to 8 space characters!

                [4mput[24m [4myour[24m .sig [4mfile[24m [4mhere[0m


        Only send this notification [4mafter[24m the files are actually available at
        the archive site.

   [1mNotify Newsgroups[0m
        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 [4mmake[24m(1) tool.
                However, it is necessary to convert makefiles into cookbooks
                using the [4mmake2cook[24m 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 [4mmake[24m(1) tool.  And Cook doesn't interpret tab
                differently to 8 space characters!

                [4mput[24m [4myour[24m .sig [4mfile[24m [4mhere[0m


        Only send this notification [4mafter[24m the files are actually available at
        the archive site.

   [1mUpdate Mailing List Info[0m
        Update the cook-users list info, by sending email

                To: majordomo@canb.auug.org.au

                newinfo cook-users [4mpassword[0m

                [4mattach[24m [4mthe[24m [4mREADME[24m [4mfile[24m [4mhere[0m


   [1mNotify Linux Announce[0m
        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 [4mmake[24m(1) tool.
                However, it is necessary to convert makefiles into cookbooks
                using the [4mmake2cook[24m 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 [4mmake[24m(1) tool.  And Cook doesn't interpret tab
                differently to 8 space characters!

                [4mput[24m [4myour[24m .sig [4mfile[24m [4mhere[0m


        Only send this notification [4mafter[24m the files are actually available at
        the archive site.

   [1mUpdate Slash Dot[0m
        Go to http://www.freshmeat.net/ and update the info for Cook.

[1mCOPYRIGHT[0m
        [4mcook[24m 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 [4mcook[24m program comes with ABSOLUTELY NO WARRANTY; for details use
        the '[4mcook[24m [4m-VERSion[24m [4mLicense[24m' command.  This is free software and you
        are welcome to redistribute it under certain conditions; for details
        use the '[4mcook[24m [4m-VERSion[24m [4mLicense[24m' command.

[1mAUTHOR[0m
        Peter Miller   E-Mail:   millerp@canb.auug.org.au
        /\/\*             WWW:   http://www.canb.auug.org.au/~millerp/



Release Notes                        Cook                        Release(Cook)
