when to update the quarks.incubator.apache.org website?

[Dale LaBossiere <dm...@gmail.com>]

README.md on https://github.com/apache/incubator-quarks-website <https://github.com/apache/incubator-quarks-website> describes the steps a committer needs to perform. 
 
The last part includes building the updated asf-site branch content and pushing that branch - resulting in an immediate update of the website.
Is that something we really want committers to do every time they merge a pull request?

— Dale

Re: when to update the quarks.incubator.apache.org website?

[Dale LaBossiere <dm...@gmail.com>]

I understand how to do it.  I’m just looking for confirmation that we really want every committer pushing every merged-PR to the live website content all the time.  There aren’t times where we wouldn’t want to push to the live site?
— Dale

> On Apr 6, 2016, at 9:01 PM, Cazen Lee <po...@gmail.com> wrote:
> 
> It's painful. I think it can be done with make CI script
> README.md on https://github.com/apache/incubator-quarks-website <
> https://github.com/apache/incubator-quarks-website> describes the steps a
> committer needs to perform.
> 
> The last part includes building the updated asf-site branch content and
> pushing that branch - resulting in an immediate update of the website.
> Is that something we really want committers to do every time they merge a
> pull request?
> 
> — Dale

Re: when to update the quarks.incubator.apache.org website?

[Cazen Lee <po...@gmail.com>]

It's painful. I think it can be done with make CI script
README.md on https://github.com/apache/incubator-quarks-website <
https://github.com/apache/incubator-quarks-website> describes the steps a
committer needs to perform.

The last part includes building the updated asf-site branch content and
pushing that branch - resulting in an immediate update of the website.
Is that something we really want committers to do every time they merge a
pull request?

— Dale