No, because the docs are built into the release too and released to the site too from the released artifact. As a practical matter, I think these docs are not critical for release, and can follow in a maintenance release. I'd retarget to 2.4.1 or untarget. I do know at times a release's docs have been edited after the fact, but that's bad form. We'd not go change a class in the release after it was released and call it the same release.
I'd still like some confirmation that someone can build and pass tests with -Pkubernetes, maybe? It actually all passed with the 2.11 build. I don't think it's a 2.12 incompatibility, but rather than the K8S tests maybe don't quite work with the 2.12 build artifact naming. Or else something to do with my env. On Mon, Oct 22, 2018 at 9:08 PM Wenchen Fan <cloud0...@gmail.com> wrote: > > Regarding the doc tickets, I vaguely remember that we can merge doc PRs after > release and publish doc to spark website later. Can anyone confirm? > > On Tue, Oct 23, 2018 at 8:30 AM Sean Owen <sro...@gmail.com> wrote: >> >> This is what I got from a straightforward build of the source distro >> here ... really, ideally, it builds as-is from source. You're saying >> someone would have to first build a k8s distro from source too? >> It's not a 'must' that this be automatic but nothing else fails out of the >> box. >> I feel like I might be misunderstanding the setup here. >> On Mon, Oct 22, 2018 at 7:25 PM Stavros Kontopoulos >> <stavros.kontopou...@lightbend.com> wrote: --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
