On Thu, Jun 1, 2017 at 2:24 PM, Benjamin Mahler <bmah...@apache.org> wrote:
> Curious to know more about what 2) looks like. > We would be maintaining a remote branch called "asf-site", similar to how we maintain remote release branches (1.0.x etc) today. The only difference would be that this branch will also include our website publish contents (e.g., in mesos/site/publish directory). Workflow would be: 1) Whenever we want to update the website, we generate/update the publish directory and do a push to that remote branch. 2) An ASF bot (gitsvnpubsub) will automatically track changes to this branch and refreshes the website at mesos.apache.org. We will automate 1) via Jenkins. Infra for 2) already exists, we just need to ask ask ASF INFRA folks to have the bot track our branch. Let me know if that doesn't clear things up.
