You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Ted Leung <tw...@sauria.com> on 2001/03/27 21:26:34 UTC
Proposal - release checklist
Hi all,
Elena and I have been talking about a checklist of things to do when doing a
Xerces-J build. Below is a lightly edited version of what we have so far.
Are
there any steps that we are missing? It would be good to have this so that
we
can start to get more people involved in the release process.
Proposed check list document for a Xerces-J Release
Change the Version.java file
Make sure the changes file is up to date - be sure to give contributors
credit for their work
Do a test build and regression test run
Tag the release in CVS
Do the final build based on that tag
Generate PGP signatures for dist binaries
Upload the binaries and signatures to the dist section of the website
Prepare release e-mail -- be sure to give contributors credit for their work
Send the release e-mail
Bugzilla
[a] create new release
[b] remove oldest release (if we are up-to 6 releases)
Website
[a] release updates
[b] FAQ updates
[c] API updates
Ted
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Proposal - release checklist
Posted by Arnaud Le Hors <le...@us.ibm.com>.
Ted Leung wrote:
>
> Do a test build and regression test run
> Tag the release in CVS
You got those two steps backward. If you don't tag before testing you're
possibly going to tag something different from what you tested.
If the build or test fails and you need to make changes it's easy enough
to bump up the tag.
--
Arnaud Le Hors - IBM Cupertino, XML Strategy Group
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Proposal - release checklist
Posted by Ted Leung <tw...@sauria.com>.
RRRRevised Proposed check list document for a Xerces-J Release
Change the following files
src/org/apache/xerces/framework/Version.java
build.xml
src/Makefile.incl
docs/dtd/entities.ent
docs/releases.xml - be sure to give contributors credit for their work
Tag the release in CVS
Do a test build and regression test run
Do the final build based on that tag
windows build
unix build (on a unix machine tomake sure no 0x0d's appear
zip and tar the tools directory [Q? are we changing this much - is there
process for this]
Generate PGP signatures for dist binaries
Upload the binaries and signatures to the dist section of the website
Update /www/xml.apache.org/dist/xerces-j/.htaccess, which directs the user
to the most recent release.
Prepare release e-mail -- be sure to give contributors credit for their work
Send the release e-mail
Bugzilla
[a] create new release
[b] remove oldest release (if we are up-to 6 releases)
Website
[a] release updates
[b] FAQ updates
[c] API updates
Commit /www/xml.apache.org/xerces-j to CVS.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Proposal - release checklist
Posted by Ted Leung <tw...@sauria.com>.
another update
----- Original Message -----
From: "Ted Leung" <tw...@sauria.com>
To: <xe...@xml.apache.org>
Sent: Wednesday, March 28, 2001 4:34 PM
Subject: Re: Proposal - release checklist
>
>
> Revised Proposed check list document for a Xerces-J Release
>
> Change the following files
> src/org/apache/xerces/framework/Version.java
> build.xml
> src/Makefile.incl
> docs/dtd/entities.ent
> docs/releases.xml - be sure to give contributors credit for their work
> Tag the release in CVS
> Do a test build and regression test run
> Do the final build based on that tag
> windows build
> unix build (on a unix machine tomake sure no 0x0d's appear
> zip and tar the tools directory [Q? are we changing this much - is
there
> process for this]
> Generate PGP signatures for dist binaries
> Upload the binaries and signatures to the dist section of the website
> Prepare release e-mail -- be sure to give contributors credit for their
work
> Send the release e-mail
> Bugzilla
> [a] create new release
> [b] remove oldest release (if we are up-to 6 releases)
> Website
> [a] release updates
> [b] FAQ updates
> [c] API updates
Commit html files to CVS.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Proposal - release checklist
Posted by Ted Leung <tw...@sauria.com>.
Revised Proposed check list document for a Xerces-J Release
Change the following files
src/org/apache/xerces/framework/Version.java
build.xml
src/Makefile.incl
docs/dtd/entities.ent
docs/releases.xml - be sure to give contributors credit for their work
Tag the release in CVS
Do a test build and regression test run
Do the final build based on that tag
windows build
unix build (on a unix machine tomake sure no 0x0d's appear
zip and tar the tools directory [Q? are we changing this much - is there
process for this]
Generate PGP signatures for dist binaries
Upload the binaries and signatures to the dist section of the website
Prepare release e-mail -- be sure to give contributors credit for their work
Send the release e-mail
Bugzilla
[a] create new release
[b] remove oldest release (if we are up-to 6 releases)
Website
[a] release updates
[b] FAQ updates
[c] API updates
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org