Switch develop to master branch

[Edward Zhang <yo...@apache.org>]

Like we discussed a few weeks back, community wants to use master branch as
development branch instead of develop branch.

We just make master to have the latest commit in develop branch, and from
now on, master branch will be the place where intensive development
happens. Any un-merged PR should be merged onto master branch.

Having master as develop branch has a few benefits like automatically to
close PR when commit and clearly to show github activities.

Going forward, we will clean develop branch. Also master branch is backed
in branch master-backup-20160907 for a while.

Thanks
Edward

Re: Switch develop to master branch

[Jayesh Senjaliya <jh...@gmail.com>]

+1, make sense.

On Wed, Sep 7, 2016 at 10:49 AM, Edward Zhang <yo...@apache.org>
wrote:

> Like we discussed a few weeks back, community wants to use master branch as
> development branch instead of develop branch.
>
> We just make master to have the latest commit in develop branch, and from
> now on, master branch will be the place where intensive development
> happens. Any un-merged PR should be merged onto master branch.
>
> Having master as develop branch has a few benefits like automatically to
> close PR when commit and clearly to show github activities.
>
> Going forward, we will clean develop branch. Also master branch is backed
> in branch master-backup-20160907 for a while.
>
> Thanks
> Edward
>