Page History

...

Propose a pull request for website updates

The final step of building the candidate is to propose a website pull request.

Start by updating the variables for the latest released version in the top-level _config.yml, and list the new release in downloads.md, linking to the source code download.

Finally, propose a pull request with these changes. (Don’t merge before finalizing the release.) 

Checklist to proceed to the next step

1. Maven artifacts deployed to the staging repository of repository.apache.org
2. Source distribution deployed to the dev repository of dist.apache.orgorg
3. Website pull request proposed to list the release

You can (optionally) also do additional verification by:

...

Once the release has been finalized, the last step of the process is to promote the release within the project and beyond. Please wait for 24h after finalizing the release in accordance with the ASF release policy.

Merge website pull request

Merge the website pull request to list the release. Make sure to regenerate the website as well, as it isn't build automatically.

Apache mailing lists

Announce on the dev@ mailing list that the release has been finished.

...

Checklist to declare the process completed

1. Website pull request to list the release merged
2. Release recorded in reporter.apache.org.
3. Completion declared on Release announced on the dev@ mailing list.

Improve the process

...