hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@cloudera.com>
Subject [DISCUSS] Moving the HBase site to use a stand-alone git repo
Date Wed, 02 Dec 2015 16:56:58 GMT
Hi Folks!

You may recall the occasional emails dev@ gets from a Jenkins job Misty set
up to make updating the website easier for us. They're titled "HBase
Generate Website" and they give a series of steps any committer can run to
push the changes live.

Misty has been investigating automating this entirely[1], so that once
updates land in the master source branch the website just updates. IMO,
this would go a long way to improving how consistently updates make it to
our primary public-facing presence.

During our conversation with INFRA (on the jira[1] and in a infra@apache
thread), the consensus seems to be that having an automated non-human
process push to a repo that doesn't contain source that might lead to a
release is acceptable. In contrast, such non-human pushing to our main repo
(even if just to the asf-site branch) is seen as higher risk that would
require a policy decision.

Is everyone (especially PMCs) fine with us moving our site to a different

Presumably something like hbase-site. The expectation is that in almost all
cases folks won't need to checkout or track this remote since the automated
job will be pushing rendered updates for us.

[1]: https://issues.apache.org/jira/browse/INFRA-10722


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message