You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@zookeeper.apache.org by "yuriipalam (via GitHub)" <gi...@apache.org> on 2026/05/26 14:14:21 UTC

Re: [PR] ZOOKEEPER-5020: Improve ZooKeeper website [zookeeper]

yuriipalam commented on PR #2373:
URL: https://github.com/apache/zookeeper/pull/2373#issuecomment-4544911196

   Everything seems to be done. The PR for changes in the `asf-site` branch is open, please take a look https://github.com/apache/zookeeper/pull/2396
   
   Once the final feedback is received, I will rebase the documentation changes.
   
   In the discussion thread we decided to architect the website in the following way:
   > Store the released docs in the `asf-site` branch. This branch stores the build being served. For example, we already do this for HBase (though it's in a separate repo, which isn't the point here), but we don't have that many old versions there. This way we don't store heavy archives in the master branch, but it comes with a tradeoff. In the master branch, we have to maintain an array of all released versions, we got more than 50 of them. We need to show the list of all previously released docs on the website. To release a new version of ZooKeeper we have to open two PRs, one for `master` and another for `asf-site`. The flow is like this: we build `master`, then we store the last build in the `asf-site` branch as other released docs. In `master`, we update the released versions array, and the current version. Then push the changes. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@zookeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org