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 people using the Kudu C++ client API in RWYW scenarios. Thanks, Alexey On Fri, Oct 7, 2016 at 12:00 PM, Dan Burkert <[email protected]> wrote: > 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 7, 2016 at 2:13 AM, Mike Percy <[email protected]> wrote: > > > On Thu, Oct 6, 2016 at 8:12 PM, Dan Burkert <[email protected]> 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 to version numbers being in embedded in the javadocs > > and elsewhere it's much easier to push the docs from the release tag, or > at > > least the release branch even if you have to cherry-pick docs past the > tag. > > Otherwise the docs will say they are for Kudu version 1.1.0-SNAPSHOT or > > whatever it currently is on the master branch. > > > > Mike > > >
