Google Git
Sign in
apache / zookeeper / refs/heads/asf-site
commit34491076c51a566a4ae5f9e9938d55b40c160bb2[log] [tgz]
authorAndor Molnar <andor@cloudera.com>Wed Nov 06 11:20:33 2024 -0600
committerAndor Molnar <andor@cloudera.com>Wed Nov 06 11:20:33 2024 -0600
tree662d29694504efdb37c2592a41c6823cbf09851a
parent05b854a8814e489c807a860a7a8f5dedb222d7cc [diff]
Website update for CVE-2024-51504
1 file changed
tree: 662d29694504efdb37c2592a41c6823cbf09851a
  1. content/
  2. .asf.yaml
  3. README.md
README.md

The production Apache ZooKeeper website

This branch houses the production Apache ZooKeeper website.

Updating this branch and pushing to the Apache git repo will cause gitpubsub to publish the site - BE CAREFULL!

How to update

Typically the website will need to be updated as part of a release. Prior to updating this branch update the “website” branch appropriately, “jekyl build”, update the product docs, APIs, etc... and then reviewed the staged site as detailed in the website branch README.

After verifying the staged site you can:

  1. git checkout asf-site - checkout this branch
  2. rm -fr content - remove the old site content
  3. mv _site content - rename the staged site directory. You should still have this from the prior staging efforts
  4. review the changes and verify that they are what you expect
  5. git add . - update git appropriately (may include git rm, etc..., as well).
  6. git commit - ensure an good commit message
  7. WARNING: review the changes you've made to git and as the next step will cause the live production site to be updated
  8. git push <origin> asf-site - point of no return.

At this point you can verify that the production site is updated and the links, etc... are functioning properly.