ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent Lintner (JIRA)" <>
Subject [jira] [Commented] (RIPPLE-84) next branch is missing
Date Wed, 13 May 2015 14:50:59 GMT


Brent Lintner commented on RIPPLE-84:

Hey [~busykai], thanks for pointing out the outdated docs. :-(

I believe this was something that happened out of simplicity, since, the `next` branch was
technically a bit redundant (or superfluous), because releases are only made from master when
a semvar version change happens, next to the fact that master is always (or should be) shippable,
especially given the decentralized nature of contributions (i.e they happen in isolation to
each other, and do not need an integration style branch).

That is just my thoughts and recollections.

IMO, I am thinking the README should be updated accordingly.


> 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