diff options
author | Michael Stapelberg <stapelberg@debian.org> | 2014-06-19 09:22:53 +0200 |
---|---|---|
committer | Michael Stapelberg <stapelberg@debian.org> | 2014-06-19 09:22:53 +0200 |
commit | 8a39ee361feb9bf46d728ff1ba4f07ca1d9610b1 (patch) | |
tree | 4449f2036cccf162e8417cc5841a35815b3e7ac5 /doc/contrib.html | |
parent | c8bf49ef8a92e2337b69c14b9b88396efe498600 (diff) | |
download | golang-8a39ee361feb9bf46d728ff1ba4f07ca1d9610b1.tar.gz |
Imported Upstream version 1.3upstream/1.3
Diffstat (limited to 'doc/contrib.html')
-rw-r--r-- | doc/contrib.html | 42 |
1 files changed, 23 insertions, 19 deletions
diff --git a/doc/contrib.html b/doc/contrib.html index 048a5d97f..6529c91d5 100644 --- a/doc/contrib.html +++ b/doc/contrib.html @@ -37,16 +37,13 @@ We encourage all Go users to subscribe to A guide for updating your code to work with Go 1. </p> -<h4 id="go1.1notes"><a href="/doc/go1.1">Go 1.1 Release Notes</a></h4> +<h4 id="release notes"><a href="/doc/go1.1">Go 1.1 Release Notes</a></h4> <p> -A list of significant changes in Go 1.1, with instructions for updating your -code where necessary. -</p> - -<h4 id="go1.2notes"><a href="/doc/go1.2">Go 1.2 Release Notes</a></h4> -<p> -A list of significant changes in Go 1.2, with instructions for updating your -code where necessary. +A list of significant changes in Go 1.1, with instructions for updating +your code where necessary. +Each point release includes a similar document appropriate for that +release: <a href="/doc/go1.2">Go 1.2</a>, <a href="/doc/go1.3">Go 1.3</a>, +and so on. </p> <h3 id="go1compat"><a href="/doc/go1compat">Go 1 and the Future of Go Programs</a></h3> @@ -61,15 +58,22 @@ Go 1 matures. <h3 id="source"><a href="https://code.google.com/p/go/source">Source Code</a></h3> <p>Check out the Go source code.</p> -<h3 id="golang-dev"><a href="http://groups.google.com/group/golang-dev">Developer Mailing List</a></h3> -<p>The <a href="http://groups.google.com/group/golang-dev">golang-dev</a> -mailing list is for discussing and reviewing code for the Go project.</p> +<h3 id="golang-dev"><a href="https://groups.google.com/group/golang-dev">Developer</a> and +<a href="https://groups.google.com/group/golang-codereviews">Code Review Mailing List</a></h3> +<p>The <a href="https://groups.google.com/group/golang-dev">golang-dev</a> +mailing list is for discussing code changes to the Go project. +The <a href="https://groups.google.com/group/golang-codereviews">golang-codereviews</a> +mailing list is for actual reviewing of the code changes (CLs).</p> + <p>For general discussion of Go programming, see <a -href="http://groups.google.com/group/golang-nuts">golang-nuts</a>.</p> +href="https://groups.google.com/group/golang-nuts">golang-nuts</a>.</p> -<h3 id="golang-checkins"><a href="http://groups.google.com/group/golang-checkins">Checkins Mailing List</a></h3> +<h3 id="golang-checkins"><a href="https://groups.google.com/group/golang-checkins">Checkins Mailing List</a></h3> <p>A mailing list that receives a message summarizing each checkin to the Go repository.</p> +<h3 id="golang-bugs"><a href="https://groups.google.com/group/golang-bugs">Bugs Mailing List</a></h3> +<p>A mailing list that receives each update to the Go <a href="http://golang.org/issue">issue tracker</a>.</p> + <h3 id="build_status"><a href="http://build.golang.org/">Build Status</a></h3> <p>View the status of Go builds across the supported operating systems and architectures.</p> @@ -77,13 +81,13 @@ systems and architectures.</p> <h2 id="howto">How you can help</h2> -<h3><a href="http://code.google.com/p/go/issues">Reporting issues</a></h3> +<h3><a href="https://code.google.com/p/go/issues">Reporting issues</a></h3> <p> If you spot bugs, mistakes, or inconsistencies in the Go project's code or documentation, please let us know by -<a href="http://code.google.com/p/go/issues/entry">filing a ticket</a> -on our <a href="http://code.google.com/p/go/issues">issue tracker</a>. +<a href="https://code.google.com/p/go/issues/entry">filing a ticket</a> +on our <a href="https://code.google.com/p/go/issues">issue tracker</a>. (Of course, you should check it's not an existing issue before creating a new one.) </p> @@ -102,8 +106,8 @@ To get started, read these <a href="/doc/contribute.html">contribution guidelines</a> for information on design, testing, and our code review process. </p> <p> -Check <a href="http://code.google.com/p/go/issues">the tracker</a> for +Check <a href="https://code.google.com/p/go/issues">the tracker</a> for open issues that interest you. Those labeled -<a href="http://code.google.com/p/go/issues/list?q=status=HelpWanted">HelpWanted</a> +<a href="https://code.google.com/p/go/issues/list?q=status=HelpWanted">HelpWanted</a> are particularly in need of outside help. </p> |