qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-21 22:04:39 -07:00
Code Releases Activity

doc: explain release and weekly tags in install.html

Browse Source 
R=r
CC=golang-dev
https://golang.org/cl/4272058
This commit is contained in:
Andrew Gerrand 2011-03-17 16:33:10 +11:00
parent 4fd41e494a
commit 929449ddaf
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/install.html
View File

@ -275,7 +275,24 @@ For the full story, consult Go's extensive
<h2 id="releases">Keeping up with releases</h2> <h2 id="releases">Keeping up with releases</h2>
<p>New releases are announced on the <a href="http://groups.google.com/group/golang-nuts">Go Nuts</a> mailing list. <p>
The Go project maintains two stable tags in its Mercurial repository:
<code>release</code> and <code>weekly</code>.
The <code>weekly</code> tag is updated about once a week, and should be used by
those who want to track the project's development.
The <code>release</code> tag is given, less often, to those weekly releases
that have proven themselves to be robust.
</p>
<p>
Most Go users will want to keep their Go installation at the latest
<code>release</code> tag.
New releases are announced on the
<a href="http://groups.google.com/group/golang-announce">golang-announce</a>
mailing list.
</p>
<p>
To update an existing tree to the latest release, you can run: To update an existing tree to the latest release, you can run:
</p> </p>
@ -286,6 +303,10 @@ $ hg update release
$ ./all.bash $ ./all.bash
</pre> </pre>
<p>
To use the <code>weekly</code> tag run <code>hg update weekly</code> instead.
</p>
<h2 id="community">Community resources</h2> <h2 id="community">Community resources</h2>
<p> <p>