This page has been prepared for Apache Lucy committers. You need committer privileges to serve as Release Manager.

If this is your first time as a Release Manager, there are some materials you should peruse to familiarize yourself with ASF release conventions.

If you have questions, ask on #lucy_dev or the dev list.

PGP Key publication (first time RMs)

NOTEThe situation with publishing KEYS is in flux and this section may no longer be relevant. See [].

If you have not already done so, append your public key to the Lucy repository KEYS file at and publish your key at The KEYS file itself contains instructions for making the necessary modifications. For more details on signing releases, see and

The KEYS file is stored on in /www/ Be careful when editing it as it is not under source control.

Community preparation

Before the Release Manager gets started, the Lucy community must complete all the tasks listed in ReleasePrep.

Helper script

Lucy has a "" helper script in devel/bin which provides the step-by-step sequence of actions necessary to perform a release. Whenever possible, it autogenerates exact commands for you to run (which often contain version-specific arguments and are troublesome to type out). It doesn't run the commands; instead it just prints them out for you to copy and paste instead of reformulate manually.

   $ ./devel/bin/ --apache-id=myapacheid --version=0.3.1-rc1 > commands.txt

Run from trunk, as the copies on the branches may or may not have been kept up to date.


From a high level, here are the stages of creating a release:

  1. Branch and tag the release candidate within version control.
  2. Build and stage the release artifacts.
  3. Vote.
  4. Publish.
  5. Announce.

The specifics of each stage are covered in

  • No labels