go1.0.3 released

[Andrew Gerrand]

We've just tagged a new Go release: go1.0.3.

This is a minor update to go1. It includes fixes to documentation and
implementation bugs. Updating to go1.0.3 will require no changes to
existing programs.

See the go1 release branch history for the complete list of changes:
http://code.google.com/p/go/source/list?name=release-branch.go1

Binary distributions are available for the FreeBSD, Linux, Mac OS X,
and Windows operating systems. To install a binary distribution,
follow these instructions:
http://golang.org/doc/install

If you prefer to build from source, follow these instructions:
http://golang.org/doc/install/source

Cheers,
Andrew

[Andrew Gerrand]

Here is a partial list of issues fixed in go1.0.3:

3906 bufio: Reader.ReadLine reusing memory of []byte output
3060 cmd/dist: emit \r in 'env -w' output
3894 cmd/gc: denies switch on array of a comparable type
3334 cmd/gc: diagnose invalid use of ...
3984 cmd/gc: error for x.(T) should offer *T if it would work
3465 cmd/gc: fix interface diagnostic
3786 cmd/gc: internal error on invalid type switch
3856 cmd/gc: no new variables errors should point at relevant operator
3899 cmd/gc: unexpected fault address when passing function value
3818 cmd/gc: wrong error message for type mismatch
3815 compress/flate: panic on index out of range
3796 crypto/tls: Intermittent errors with OpenSSL client
3777 database/sql reuses bad connections +patch
3869 flag: ignores failures when the flag is not parseable into a boolean
3752 fmt: Printf, %s output of nil get poisoned by struct pointers
3898 go/ast: Fprint misbehaves with user-provided data.
3914 go/build: reads build tags lines even in the middle of source files
3870 go/printer crashes if it encounters a FuncType with nil Params field
3851 godoc: click on html link for method named Index takes you to
package index, and not method
3916 image/jpeg: Invalid SOS parameters for sequential JPEG
4084 image/jpeg: unable to decode jpeg image with error: "unsupported
JPEG feature: unknown marker"
3843 internal compiler error: typename <T>
3782 misc/emacs: go-mode.el does not work handle temp directories
besides /tmp/ for gofmt
3724 net/http/client.go - Client.CheckRedirect does not have the
claimed error behavior
3892 net/http/httputil: unit test failure
3538 net/http: CONNECT method invali
3414 net/http: FileServer returns 304 Not Modified on modified index pages
3663 net/http: client connection close request not echoed in response headers
1967 net/http: connection never closes
3946 net/http: excessive mutex contention
3644 net/http: http Client regression
3842 net/http: parent directory listing vulnerability
3784 net/http: support multiple byte ranges
3828 os: IsExist() doesn't detect "file already exists" os.Rename()
error for windows
3860 os: data race in epipecheck()
3969 os: data race on os.Process.done
3649 os: report more precise error from StartProcess
3879 pprof script doesn't work under Windows.
3853 reflect: PkgPath regression for byte
3871 runtime, cgo: cgo call to setgid hangs on GNU/Linux
3718 runtime: memset/memmove clobbers r9/r10 on Linux/ARM
3852 spec: evaluation order in assignments return statements
3763 spec: inconsistent description in "Qualified identifiers" section
3779 spec: x.f for nil x causes runtime panic, is not illegal
3849 syscall: Accept sometimes returns address family not supported by
protocol family error on OS X
3830 testing: cannot print many-linestrings
3850 text/template: type checker bug with missing map keys
3967 time: data race on local Location
3971 various: defer Close() before err check

To read more about an issue, visit http://golang.org/issue/N where N
is the issue number.

Andrew

[Paddy Foran]

If an issue is marked as fixed in the issue tracker and links to a commit, that commit should be included in this release, correct?

Just wanted to make sure, as I didn't see a note about embedding anonymous structs in JSON (issue 3609: http://golang.org/issue/3609), and I'm curious if it made the cut.

--

[Paddy Foran]

I'm sorry, I screwed that up. Is issue 3069: http://golang.org/issue/3069. Sorry.

[Andrew Gerrand]

On Monday, 24 September 2012 14:17:21 UTC-5, Paddy Foran wrote:

If an issue is marked as fixed in the issue tracker and links to a commit, that commit should be included in this release, correct?

I made the list using this command:

hg log -v -r go1.0.2:tip -b release-branch.go1 | egrep '^Fixes issue' | awk '{ print $3 }' | sort | cut -b -4 | uniq | xargs -n 1 issue | egrep '^[0-9]'

and then editing the output down. (Get the issue command with "go get code.google.com/p/rsc/cmd/issue")

So it's a list of all issues fixed by changes included in the release branch since go1.0.2. It's possible that some of these issues were closed and then later re-opened, and as such are not actually fixed in go1.0.3, but I tried to remove those.

Andrew

[Paddy Foran]

Ah, thanks for the info. I've checked the source file in 1.0.3, and don't see the changes, so I guess it didn't make the cut. Possibly because it could be considered an API change, and therefore will have to wait until Go 1.1?

But I'm getting off topic. Thanks for the release. :)

--
 
 

[Andrew Gerrand]

On 24 September 2012 14:31, Paddy Foran <foran...@gmail.com> wrote:
> Ah, thanks for the info. I've checked the source file in 1.0.3, and don't
> see the changes, so I guess it didn't make the cut. Possibly because it
> could be considered an API change, and therefore will have to wait until Go
> 1.1?

Correct. It's an API change and it'll be in 1.1.

Andrew