From: Shenghou Ma
-A list of significant changes in Go 1.1, with instructions for updating your -code where necessary. -
- --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: Go 1.2, Go 1.3, +and so on.
Check out the Go source code.
-The golang-dev -mailing list is for discussing and reviewing code for the Go project.
+The golang-dev +mailing list is for discussing code changes to the Go project. +The golang-codereviews +mailing list is for actual reviewing of the code changes (CLs).
+For general discussion of Go programming, see golang-nuts.
+href="https://groups.google.com/group/golang-nuts">golang-nuts. -A mailing list that receives a message summarizing each checkin to the Go repository.
+A mailing list that receives each update to the Go issue tracker.
+View the status of Go builds across the supported operating systems and architectures.
@@ -77,13 +81,13 @@ systems and architectures.If you spot bugs, mistakes, or inconsistencies in the Go project's code or documentation, please let us know by -filing a ticket -on our issue tracker. +filing a ticket +on our issue tracker. (Of course, you should check it's not an existing issue before creating a new one.)
@@ -102,8 +106,8 @@ To get started, read these contribution guidelines for information on design, testing, and our code review process.-Check the tracker for +Check the tracker for open issues that interest you. Those labeled -HelpWanted +HelpWanted are particularly in need of outside help.