Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <CAB8hLak4=5ywVQ9pf1UsgmTekucYRY2OW1R2VyYwCLT6sUkanw@mail.gmail.com>
References: <CAB8hLak4=5ywVQ9pf1UsgmTekucYRY2OW1R2VyYwCLT6sUkanw@mail.gmail.com>
From: Sean Busbey <busbey@apache.org>
Date: Mon, 17 Jul 2017 09:00:09 -0500
Message-ID: <CAN5cbe5ESGpG6soKtJN3DmR3=Cd4SuaL4TmEnm4yrpCOdFL9xQ@mail.gmail.com>
Subject: Re: One problem about document change
To: dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary="001a114ddf105242f9055483d229"
archived-at: Mon, 17 Jul 2017 14:00:35 -0000

--001a114ddf105242f9055483d229
Content-Type: text/plain; charset="UTF-8"

Contributors and committers usually only worry about making documentation
changes to the master branch.

When it comes time to spin up release candidates for a new version, the
release manager usually copies the then-current state of documentation in
the master branch to the branch they'll be working from (in this case
branch-2). Sometimes that documentation is also tailored further to the
release line (e.g. to remove irrelevant feature discussion).

On Sun, Jul 16, 2017 at 9:16 AM, Guanghao Zhang <zghaobac@gmail.com> wrote:

> Hi, folks
>
> Now I am working on the asynchronous admin which is part of asynchronous
> client. The asynchronous client feature were pushed to branch-2 and master
> branch. But one confuse thing is about the document change. The book site
> is generated by master branch's code. So the document change should only be
> pushed to master branch? Or it should be pushed to branch-2 and master
> both, because this feature was merged to branch-2, too? I am not sure about
> this, so look forward to you guys' idea. Thanks.
>
> Guanghao Zhang
>

--001a114ddf105242f9055483d229--