Hi,
We're happy to announce the first release candidate for Apache Kudu 1.0.1.
This release includes bug fixes and documentation updates since the 1.0.0
release.
The is a source-only release. The artifacts were staged here:
https://dist.apache.org/repos/dist/dev/kudu/1.0.1-RC1/
It was built fro
Dan,
Thank you for fast turn-around and picking up that update!
Best regards,
Alexey
On Fri, Oct 7, 2016 at 12:16 PM, Dan Burkert wrote:
> Thanks for the heads up; I made sure I got everything that touched /docs
> but didn't think about header only changes!
>
> - Dan
>
> On Fri, Oct 7, 2016
Thanks for the heads up; I made sure I got everything that touched /docs
but didn't think about header only changes!
- Dan
On Fri, Oct 7, 2016 at 12:08 PM, Alexey Serbin wrote:
> Hi Dan,
>
> I saw there was a doc-only change cherry-picked into the 1.0.1: Adar's
> update on master migration doc,
Hi Dan,
I saw there was a doc-only change cherry-picked into the 1.0.1: Adar's
update on master migration doc, b783627.
On that note, if you haven't cut RC yet, consider cherry-picking just
another doc-only update: b70d362. It's not crucial for the functionality,
but it might be useful for peopl
I've pulled in all of the doc fixups between 1.0.0 and now into 1.0.x. I
cherry-picked KUDU-1681, but none of the other I listed yesterday, since
the consensus seems to be that they are extremely unlikely to occur on a
real cluster. I'll be cutting the RC later this afternoon.
- Dan
On Fri, Oct
Hello all,
Dinesh Bhat and I worked together offline to come up with a high level
scoping document around disaster recovery tools. Please take a look and
feel free to provide comments / additions in the Google Doc located here:
https://s.apache.org/7K48
Regards,
Mike
On Thu, Oct 6, 2016 at 8:12 PM, Dan Burkert wrote:
> I'll make sure we release a new build of the website since a lot of docs
> have changed. My understanding is that this can be decoupled from the
> actual release branch, so doc-only changes don't need to be backported.
>
In my experience due
