File tree 2 files changed +10
-2
lines changed
2 files changed +10
-2
lines changed Original file line number Diff line number Diff line change @@ -49,6 +49,14 @@ <h3 id="go1.7.minor">Minor revisions</h3>
49
49
1.7.1 milestone</ a > on our issue tracker for details.
50
50
</ p >
51
51
52
+ < p >
53
+ go1.7.2 (released 2016/10/17) includes fixes to the compiler, runtime,
54
+ and the < code > crypto/cipher</ code > , < code > crypto/tls</ code > ,
55
+ < code > net/http</ code > , and < code > strings</ code > packages.
56
+ See the < a href ="https://github.com/golang/go/issues?q=milestone%3AGo1.7.2 "> Go
57
+ 1.7.2 milestone</ a > on our issue tracker for details.
58
+ </ p >
59
+
52
60
< h2 id ="go1.6 "> go1.6 (released 2016/02/17)</ h2 >
53
61
54
62
< p >
Original file line number Diff line number Diff line change @@ -203,7 +203,7 @@ <h2 id="fetch">Fetch the repository</h2>
203
203
Change to the directory that will be its parent
204
204
and make sure the < code > go</ code > directory does not exist.
205
205
Then clone the repository and check out the latest release tag
206
- (< code class ="versionTag "> go1.7.1 </ code > , for example):</ p >
206
+ (< code class ="versionTag "> go1.7.2 </ code > , for example):</ p >
207
207
208
208
< pre >
209
209
$ git clone https://go.googlesource.com/go
@@ -391,7 +391,7 @@ <h2 id="releases">Keeping up with releases</h2>
391
391
< a href ="//groups.google.com/group/golang-announce "> golang-announce</ a >
392
392
mailing list.
393
393
Each announcement mentions the latest release tag, for instance,
394
- < code class ="versionTag "> go1.7.1 </ code > .
394
+ < code class ="versionTag "> go1.7.2 </ code > .
395
395
</ p >
396
396
397
397
< p >
You can’t perform that action at this time.
0 commit comments