head	1.6;
access;
symbols
	HORDE_2_0_RC2:1.5.2.1
	RELENG_2:1.5.0.2
	HORDE_2_0_0_RC1:1.5
	HORDE_1_3_4:1.5
	HORDE_1_3_3:1.3;
locks; strict;
comment	@# @;


1.6
date	2001.11.10.11.22.33;	author bjn;	state Exp;
branches;
next	1.5;

1.5
date	2001.02.07.12.50.30;	author bjn;	state Exp;
branches
	1.5.2.1;
next	1.4;

1.4
date	2001.02.02.12.48.42;	author bjn;	state Exp;
branches;
next	1.3;

1.3
date	2000.11.06.16.22.09;	author bjn;	state Exp;
branches;
next	1.2;

1.2
date	2000.10.18.20.34.47;	author bjn;	state Exp;
branches;
next	1.1;

1.1
date	2000.09.29.14.31.05;	author bjn;	state Exp;
branches;
next	;

1.5.2.1
date	2001.11.15.22.42.37;	author chuck;	state Exp;
branches;
next	1.5.2.2;

1.5.2.2
date	2001.11.20.15.38.00;	author bjn;	state dead;
branches;
next	;


desc
@@


1.6
log
@Minor step toward getting this current.
@
text
@===========================================================================
|| Horde Release Process Notes                                           ||
===========================================================================

$Horde: horde/docs/RELEASE,v 1.5 2001/02/07 12:50:30 bjn Exp $


Here are the steps I use when cutting a new release:

-   Examine */docs/CHANGES files:

    --  Add the word SECURITY in front of any security-related changes,
        and move them to the top, to draw attention to them.

    --  Cull out the most important ones, and prepare the text of an
        announcement.

-   Set the CVSROOT environment variable to a user with commit privs, and
    change to an empty directory.

-   Create the tarballs using (HEAD) horde/scripts/make-tarball.pl:

    --  Must be run as root (to set file ownership).

    --  Can optionally add "--nocommit" to do a "dry run" that will not
        make any CVS changes.

    --  Example commands (omit "--branch" when building HEAD):

        # make-tarball.pl --module=horde --version=1.2.<n> --branch=STABLE_1_2
        # make-tarball.pl --module=imp --version=2.2.<n> --branch=STABLE_2_2

-   Get the MD5 checksum of the resulting tarballs, and add to the
    announcement text.

-   Copy the resulting tarballs to ftp://ftp.horde.org/pub/<module>/tarballs
    (the /usr/local/ftp/pub/... directory on the horde.org server):

    --  Make sure group is "ftp" and permissions are "rw-rw-r--" so that
        other team members can write to them.

    --  Update the "latest" symbolic links; for example:

        $ cd .../pub/horde/tarballs
        $ ln -sf horde-1.2.<n>.tar.gz horde-latest.tar.gz
        $ cd .../pub/imp/tarballs
        $ ln -sf imp-2.2.<n>.tar.gz imp-latest.tar.gz

    --  Update the .../pub/<module>/tarballs/README files.

    --  Move previous versions to the "old" subdirectory.

-   Update the web site (hordeweb CVS directory):

    --  Edit top-level hordeweb/main.html

    --  For IMP, under hordeweb/imp and edit:

        2.3/2001 (or current year) 2.3/latest.html 2.3/supported.html
        download/download.html

    --  For Turba, under hordeweb/turba and edit:

        content.txt download/download.html

-   Publish the announcement to the relevant Horde lists (including
    "announce").

-   Create a freshmeat.net announcement.

-   Add new sentinels to the top of the <module>/docs/CHANGES files.

    [TO DO: automate this task in the make-tarball.pl script.]

[Note: as of 9/29/2000, the make-tarball.pl script should now
automatically update the <module>/lib/version.php files, so this
doesn't need to be done manually any more.]
@


1.5
log
@New horde-latest.README sym. links (RPMs) so FAQ doesn't have to be updated.
@
text
@d5 1
a5 1
$Horde: horde/docs/RELEASE,v 1.4 2001/02/02 12:48:42 bjn Exp $
d55 1
a55 1
    --  For IMP, check out hordeweb/imp and edit:
d57 3
a59 1
        2.2/2001 (or current year) 2.2/latest.html 2.2/supported.html
d61 4
@


1.5.2.1
log
@MFH rev 1.6: updates
@
text
@d5 1
a5 1
$Horde: horde/docs/RELEASE,v 1.6 2001/11/10 11:22:33 bjn Exp $
d55 1
a55 1
    --  Edit top-level hordeweb/main.html
d57 1
a57 3
    --  For IMP, under hordeweb/imp and edit:

        2.3/2001 (or current year) 2.3/latest.html 2.3/supported.html
a58 4

    --  For Turba, under hordeweb/turba and edit:

        content.txt download/download.html
@


1.5.2.2
log
@Build scripts/docs should only live in HEAD branch.
@
text
@d5 1
a5 1
$Horde: horde/docs/RELEASE,v 1.5.2.1 2001/11/15 22:42:37 chuck Exp $
@


1.4
log
@Welcome to 2001.
@
text
@d5 1
a5 1
$Horde: horde/docs/RELEASE,v 1.3 2000/11/06 16:22:09 bjn Exp $
a65 4

    [TO DO: automate this task in the make-tarball.pl script.]

-   Keep hordeweb/faq/admin/install/answers.txt RPM version up to date.
@


1.3
log
@Some notes on version-keeping.
@
text
@d5 1
a5 1
$Horde: horde/docs/RELEASE,v 1.2 2000/10/18 20:34:47 bjn Exp $
d57 1
a57 1
        2.2/2000 2.2/latest.html 2.2/supported.html
@


1.2
log
@Add hordeweb/imp/2.2/supported.html to the list of files with version #.
@
text
@d5 1
a5 1
$Horde: horde/docs/RELEASE,v 1.1 2000/09/29 14:31:05 bjn Exp $
d66 6
@


1.1
log
@Here are the steps I use when cutting a new release.
@
text
@d5 1
a5 1
$Horde$
d57 2
a58 1
        2.2/2000 2.2/latest.html download/download.html
@

