head	1.2;
access;
symbols
	JSERV_1_1_2:1.2
	JSERV_1_1_1:1.2
	JSERV_1_1_1b1:1.2
	JSERV_1_1:1.2
	V1_1b3:1.2
	V1_1b2:1.2
	V1_1b1:1.2
	CONFIG:1.2.0.4
	JSERV1_0:1.2
	JSERV1_0FC1:1.2
	JSERV1_0B5:1.2
	JSERV1_0B4:1.2
	JSERV1_0B3:1.2
	JSERV1_1DEV:1.2.0.2;
locks; strict;
comment	@# @;


1.2
date	99.01.19.05.29.28;	author jonbolt;	state Exp;
branches;
next	1.1;

1.1
date	99.01.19.05.06.49;	author jonbolt;	state Exp;
branches;
next	;


desc
@@


1.2
log
@found more friggen version numbers to change...we really should fix this
to rely on a central version resource...maybe a VERSION file at the root
of the build directory...even better...maybe a sed/awk script could be
created that does a find/replace on all of the files...
@
text
@Use the scripts in these directories to easily create Apache JServ 
packages for distribution. These are provided so that anybody can pick 
up the ball and release new versions without needing to learn a complex 
process. This is bazaar style development.

The following files must be modified to reflect the current version of 
Apache JServ before creating a package for release:

configure.in:
     change version info on line 19

src/scripts/package/tar.gz/snap.sh:
     change version info on line 5

src/scripts/package/zip/make.package.bat:
     change version info on line 11

src/c/jserv.h:
     change version info on line 81

src/java/org/apache/jserv/JServ.java:
     change version info on line 96


@


1.1
log
@this file describes what is needed in order to do a release of a package
@
text
@d9 9
@

