Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: master -> main

...

For patch releases (x.y.z), run the release wizard script from the release branch, e.g. branch_8_8; for minor release, run the release wizard from the major version stable branch, e.g. branch_8x; for major release, run the release wizard from master.main.

Plan for the release to take at least 5 days, but probably closer to 8-10 days if the vote period overlaps with a weekend or holiday (or an RC fails, resetting the timeline on the vote):

  • 1-2 days to build the first RC
  • At least 3 days vote for the RC
  • 1 additional day waiting time once the RC vote passes for the release artifacts to find their way to all the mirrors
  • Few hours after the release to tidy up for the next release

The release wizard prompts whether you want to do the release in a new, clean checkout under ~/.lucene-releases. Absolutely do this and don't try to save disk or network I/O by using your normal working dir for the project!

To speed up tests while building the RC, you can increase parallelism by adding the following settings to your ~/lucene.build.properties

...

Once you reach the publish artifacts step, you'll need to wait 24hrs before moving on to the next step, so plan accordingly.

Lastly, please Please do the next RM a favor and complete all of the Post release steps in a timely manner. If you skip any of these steps, then the next RM may encounter weird failures in the release wizard that they may not understand the problem, esp. for new RMs. Report any issues you find in JIRA when doing the release so we can improve the release process.

Lastly, please add any additional advice you have for the next RM to this section.