Release Process

Every project needs a release process. This document is based on an email here.

Here are some references for fleshing out this process.

• The overarching Apache release process .
• Guidance on Apache Incubator release process.

Release contents

Distributables will be prefixed by apache-kato-incubating-

API

• kato.api - The API interfaces and the services framework
• The JSR-326 specification.
• TCK - harness and tests.

Implementations

• kato.cjvmti - The JSR-326 API JVMTI implementation
• kato.native.cjvmti - The JVMTI agent.
• kato.hprof - The implementation of JSR-326 API for hprof.

Tech demos:

• kato.jdi - The JDI connector
• kato.tools.katoview - The command line tool.

Eclipse tech demos:

• kato.explorer - The API explorer for Eclipse
• kato.hexeditor - the hexeditor
• kato.rtexplorer - the java runtime explorer.
• JDI connector eclipse plugin.

The Release Process

1. Assess the state of what we have and fix it up where necessary.
2. Create LICENSE and NOTICE files, where necessary.
3. Get the jobs building on Apache's Hudson server (except for where that is not possible, e.g. Windows builds).
4. Write documentation for it all. Shouldn't be too onerous.
5. Create a job on Hudson that will package all of the other builds, in the process:
   1. generating checksums
   2. Incorporate licenses and notices
   3. generate source and binary distributables.
6. Sign distributables
7. Make available as a candidate release (under a home directory on people.apache.org?)
8. Call a vote on kato-dev mailing list.
9. Formally ask the Incubator PMC permission to do a release
10. Repeat and revise previous steps until acceptable.
11. Put distributions in appropriate place (http://www.apache.org/dist/incubator/kato)
12. Modify website to include "downloads" page with links to current release.
13. Announce the release to the world.