[
https://issues.apache.org/jira/browse/HBASE-24733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156998#comment-17156998
]
Nick Dimiduk commented on HBASE-24733:
--------------------------------------
That would work too. This seems it happens infrequently enough that the push
method would be fine, but if we have the resources, I'm okay with a
polling-based approach.
> create-release should stage PR with documentation changes
> ---------------------------------------------------------
>
> Key: HBASE-24733
> URL: https://issues.apache.org/jira/browse/HBASE-24733
> Project: HBase
> Issue Type: Task
> Components: community
> Reporter: Nick Dimiduk
> Priority: Major
>
> {{create-release}} has all the bits it needs to put together commits (and
> PRs) with documentation changes for both {{hbase.git}} and {{hbase-site.git}}
> that accompany a release candidate. Let's automate this as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)