Clarify state of `v1` branch

main
Dan Buch 8 years ago
parent 8af550936f
commit 61e5e9362f
No known key found for this signature in database
GPG Key ID: FAEF12936DD3E3EC

@ -34,10 +34,11 @@ export PATH=$PATH:$GOPATH/bin
There is currently a long-lived branch named `v2` that is intended to land as There is currently a long-lived branch named `v2` that is intended to land as
the new `master` branch once development there has settled down. The current the new `master` branch once development there has settled down. The current
`master` branch (what will become `v1`) is being manually merged into `v2` on an `master` branch (current mirrored as `v1`) is being manually merged into `v2` on
irregular human schedule, but generally if one wants to "upgrade" to `v2` *now* an irregular human-based schedule, but generally if one wants to "upgrade" to
and accept the volatility (read: "awesomeness") that comes along with that, `v2` *now* and accept the volatility (read: "awesomeness") that comes along with
please use whatever version pinning of your preference, such as via `gopkg.in`: that, please use whatever version pinning of your preference, such as via
`gopkg.in`:
``` ```
$ go get gopkg.in/codegangsta/cli.v2 $ go get gopkg.in/codegangsta/cli.v2

Loading…
Cancel
Save