ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arzhan Kinzhalin (JIRA)" <>
Subject [jira] [Commented] (RIPPLE-84) next branch is missing
Date Wed, 13 May 2015 15:06:00 GMT


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:
>             Project: Apache Ripple
>          Issue Type: Github Integration
>            Reporter: Arzhan Kinzhalin
> {{}} [mentions|]
{{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 (fetch)
> github (push)
> origin (fetch)
> origin (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

View raw message