[
https://issues.apache.org/jira/browse/APEXCORE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194389#comment-15194389
]
ASF GitHub Bot commented on APEXCORE-382:
-----------------------------------------
GitHub user sashadt opened a pull request:
https://github.com/apache/incubator-apex-malhar/pull/210
APEXCORE-382 #resolve Adding new documentation steps to avoid build a…
…rtifacts on in site master branch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sashadt/incubator-apex-malhar
docs.APEXCORE-382
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-malhar/pull/210.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #210
----
commit a789bee79f2b2f97d66fb1c0bcac062bdb1d13d5
Author: sashadt <[email protected]>
Date: 2016-03-14T23:35:23Z
APEXCORE-382 #resolve Adding new documentation steps to avoid build
artifacts on in site master branch
----
> Update document deployment process to avoid versioning generated artifacts in
> master branch
> -------------------------------------------------------------------------------------------
>
> Key: APEXCORE-382
> URL: https://issues.apache.org/jira/browse/APEXCORE-382
> Project: Apache Apex Core
> Issue Type: Task
> Reporter: Sasha Parfenov
> Assignee: Sasha Parfenov
> Labels: documentation
>
> Right now both Apex Core and Malhar documentation is built, and then checked
> into the master branch. This has two negative outcomes, including:
> * adding build artifacts to master
> * potential confusion over where documents sources should be edited
> To avoid these issues, new process will be put in place, where generated
> documentation will be checked directly into the asf-site branch, and merged
> with "content" as part of the build.sh script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
