Publish 0.4.0-incubating release

[jbonofre]

No description provided.

[jbonofre]

R: @davorbonaci

[asfbot]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/beam_PreCommit_Website_Test/146/
--none--

[asfbot]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/beam_PreCommit_Website_Stage/189/

Jenkins built the site at commit id 76ee659 with Jekyll and staged it here. Happy reviewing.

Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again.

[kennknowles]

So the second Javadoc commit is actually a second try as part of 0.4.0-incubating, right?

I would prefer the "Publish 0.4.0-incubating release" commit to not touch generated files. Since the Javadoc is overwritten anyhow, can you remove it from this commit?

Something like this (I haven't tested it)

git rebase -i
# edit that commit
git checkout -- documentation/sdks/javadoc
git commit --amend
git rebase --continue

[jbonofre]

The second commit is updated based on the RC3 tag whereas the first commit was on the RC1 tag.