Re: [afp-renderer-developers] Release procedures

[Joe S. <jo...@ex...>]

On Sun, 2004-11-21 at 12:11, Pete Townsend wrote:
> Sounds good, suggest we document this on the web site?

I'm more inclined to check it in as a top level file in the module. This
sort of information is of no interest to users or casual browsers, but
people who need to know this information will already have a workspace.

> Also I've added and
> XML2AFP class and BAT file to the project. I'll start adding some test cases
> so that we can have a fully functional demo once we get the fonts.

Nice. I'll look over it when I get a chance.

Cheers,
Joe


> ----- Original Message ----- 
> From: "Joe Schmetzer" <jo...@ex...>
> To: <afp...@li...>
> Sent: Saturday, November 20, 2004 9:29 PM
> Subject: [afp-renderer-developers] Release procedures
> 
> 
> > Just checked into CVS... the ant build now supports a "release" target,
> > which should simplify building release.
> >
> > The following is a procedure/checklist which I think should be followed
> > for an official release. This procedure uses version 1.1.0 as an
> > example, and assumes a valid environment with CVSROOT, JAVA_HOME and
> > ANT_HOME correctly defined.
> >
> > 1) Make sure CHANGES, README, etc are up to date. Edit build.properties
> > to reflect the new release version, and check it into HEAD.
> >
> > dist.version = 1.1.0
> > dist.type =
> > ...
> > cvs ci -m "Release 1.1.0" build.properties
> >
> > 2) Tag the new release in CVS.
> >
> > cvs rtag -rHEAD AFP_RENDERER_1_1_0 afp-fop-src
> >
> > 3) Checkout a clean workspace using the tag and cd into it
> >
> > cvs co -rAFP_RENDERER_1_0_0 afp-fop-src
> > cd afp-fop-src
> >
> > 4) Run the release target in ant. This should create a new file called
> > afp-renderer-1.1.0.zip in the current directory. This is the file to be
> > published.
> >
> > ant release
> >
> > 5) Publish the release using the sourceforge admin interface.
> >
> > 6) To avoid accidentally creating a new release of the same name,
> > immediately bump up the build.properties version properties to the next
> > incremental release and check in.
> >
> > dist.version = 1.1.1
> > dist.type = -dev
> > ...
> > cvs ci -m "Release 1.1.1-dev" build.properties
> >
> > I think that's about it. Thoughts? Comments?
> >
> > Cheers,
> > Joe
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: InterSystems CACHE
> > FREE OODBMS DOWNLOAD - A multidimensional database that combines
> > robust object and relational technologies, making it a perfect match
> > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> > _______________________________________________
> > afp-renderer-developers mailing list
> > afp...@li...
> > https://lists.sourceforge.net/lists/listinfo/afp-renderer-developers
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> afp-renderer-developers mailing list
> afp...@li...
> https://lists.sourceforge.net/lists/listinfo/afp-renderer-developers