[
https://issues.apache.org/jira/browse/RIPPLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542060#comment-14542060
]
Arzhan Kinzhalin commented on RIPPLE-84:
----------------------------------------
[~brentlintner], second that! {{next}} could potentially be useful if work on
stabilizing the release and work on next release is done in parallel. Even
then, it perhaps easier to simply cut {{release}} branch, tag it once done and
then merge back to {{master}}, then delete. So maybe contribution guideline
could simplified to ask to contribute to {{master}} instead of confusing casual
contributor with details of internal branching policies (which may change over
time).
> next branch is missing
> ----------------------
>
> Key: RIPPLE-84
> URL: https://issues.apache.org/jira/browse/RIPPLE-84
> Project: Apache Ripple
> Issue Type: Github Integration
> Reporter: Arzhan Kinzhalin
>
> {{README.md}}
> [mentions|https://github.com/apache/incubator-ripple/blob/master/README.md#contributing]
> {{next}} branch which should be merge target for all the PRs, it is,
> however, missing both from Apache git server and its GitHub mirror:
> {code}
> $ git remote -vv
> github [email protected]:apache/incubator-ripple.git (fetch)
> github [email protected]:apache/incubator-ripple.git (push)
> origin https://git-wip-us.apache.org/repos/asf/incubator-ripple.git (fetch)
> origin https://git-wip-us.apache.org/repos/asf/incubator-ripple.git (push)
> <...skip...>
> $ git fetch origin
> $ git fetch github
> $ git branch -r | grep "\(github\|origin\)"
> github/master
> origin/HEAD -> origin/master
> origin/master
> {code}
> It seems that it was there at some point, some issues and PRs mention it, but
> now it's gone. Perhaps, it would be nice to restore it. Having everything on
> a single branch is awkward.
> P.S. Filing it as "Github integration" as it seems the most appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
