Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.
The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.html
To learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.html
Go 1 is available as binary distributions 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
The Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORS
We also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
Awesome news congratulations!!
I was hoping for a bit more PR around this release: "here's how we use
Go to great things!" "here's why Go is the best at what it does" and
so on. Will there be more videos like the ones that were released when
Go first was announced?
Big Grats to th Go team, and a big thank you to all the contributers.
Cheers the noo,
Graham
We've just tagged a new Go release: go1.
On Thu, 2012-03-29 at 03:03 +1100, Andrew Gerrand wrote:
> We've just tagged a new Go release: go1.
[...]
Is this supposed to happen when updating a pre-exiting clone...
|> hg pull
pulling from https://go.googlecode.com/hg
searching for changes
no changes found
|> hg update go1
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
|> hg status
|> ( cd src && clean.bash )
./clean.bash: line 8: go: command not found
cannot find $GOTOOLDIR/dist; nothing to clean
|> ( cd src && all.bash )
# Building C bootstrap tool.
cmd/dist
# Building compilers and Go bootstrap tool for host, linux/amd64.
go tool dist: /home/Checkouts/Mercurial/Go/src/cmd/cov should not exist in release build
|>
>
> Have fun. (And tell your friends! ;-)
Already doing this... :-)
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel...@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Does the Go 1 compatibility document answer your questions?
http://golang.org/doc/go1compat.html
What does "hg identify" say?
Congratulations to everyone involved
Is this supposed to happen when updating a pre-exiting clone...
|> hg pull
pulling from https://go.googlecode.com/hg
searching for changes
no changes found
|> hg update go1
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
|> hg status
|> ( cd src && clean.bash )
./clean.bash: line 8: go: command not found
cannot find $GOTOOLDIR/dist; nothing to clean
|> ( cd src && all.bash )
# Building C bootstrap tool.
cmd/dist
# Building compilers and Go bootstrap tool for host, linux/amd64.
go tool dist: /home/Checkouts/Mercurial/Go/src/cmd/cov should not exist in release build
Yep, we've got a lot of stuff like this planned.
Point releases will be go1.0.1, go1.0.2, and so on.
Milestone releases of go1 will be go1.1, go1.2, and so on.
Andrew
On 29 March 2012 03:21, Jan Mercl wrote:
> How will be upcoming fixes handled? In weekly.xxxxx or say go1_1_xxxx or
> what? Which branch/tag to follow? Naturally it's best to code everything
> against Go 1 now, but will be the fixes backported or something? Please
> advice the "now" best practice for developers, thank you.Does the Go 1 compatibility document answer your questions?
http://golang.org/doc/go1compat.html
Point releases will be go1.0.1, go1.0.2, and so on.
Milestone releases of go1 will be go1.1, go1.2, and so on.
Awesome congratulations!!
Congratulations! Really a big news.
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
I went back to the weekly tag to get something working.
> On Wed, Mar 28, 2012 at 12:41 PM, minux <minu...@gmail.com> wrote:
>
>
> On Thu, Mar 29, 2012 at 12:34 AM, Russel Winder
> <rus...@winder.org.uk> wrote:
> Is this supposed to happen when updating a pre-exiting
> clone...
>
> |> hg pull
> pulling from https://go.googlecode.com/hg
> searching for changes
> no changes found
>
> |> hg update go1
> 0 files updated, 0 files merged, 0 files
> removed, 0 files unresolved
> should be "hg update release-branch.go1"
OK, on the one hand this could be seen as me not knowing Mercurial well
enough. On the other hand it shows that Mercurial tags are broken in
that the tag, when used, does not cause the appropriate change of
branch. Clearly this isn't a Go problem, except that it affects Go
bleeding edge users.
> |> hg status
>
> |> ( cd src && clean.bash )
> ./clean.bash: line 8: go: command not found
> cannot find $GOTOOLDIR/dist; nothing to clean
>
> |> ( cd src && all.bash )
> # Building C bootstrap tool.
> cmd/dist
>
> # Building compilers and Go bootstrap tool for
> host, linux/amd64.
> go tool
> dist: /home/Checkouts/Mercurial/Go/src/cmd/cov should
> not exist in release build
> Blame hg, it should have deleted these directories. You have
> to delete src/cmd/{cov, prof},
> src/pkg/{old,exp}, and then your build will succeed.
>
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel...@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
The Mercurial tags are working just fine.
In a rare event, minux was incorrect. You do not need to use
hg update release-branch.go1. Using hg update go1 is fine.
The 'clean.bash' in your original post failed because clean.bash
is only usable after you do a build now. A build with make.bash
or all.bash always starts from a clean slate anyway.
The 'all.bash' failed because your client had some stale binaries
in directories like src/cmd/cov, so the hg up, while it did delete
the tracked files, left the directories with the object dregs behind.
The build requires that those directories be gone, since they are
not part of the official Go 1. If you delete the directories that it
complains about by hand, all will be well.
These problems are primarily due to an impedance mismatch:
Mercurial is really a version control system and we're making it
work as a software distribution system. Most of the time they're
close enough not to care, but not always.
Sorry for the trouble.
Russ
--
André Moraes
http://andredevchannel.blogspot.com/
Dave
We've just tagged a new Go release: go1.
Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.
The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.html
To learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.html
Go 1 is available as binary distributions 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
The Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORS
We also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
Congratulations are in order!
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew
Huge congrats to the team! I am very excited about using this and will start encouraging use of Go on any appropriate projects I come across. I will continue to use it for my own personal projects, as well. I've found App Engine to be very helpful to demonstrate new ideas to co-workers, as well. Keep up the great work!
I'm not aware of any, but perhaps someone on this list would be
interested in starting one with you :-)
Andrew
We've just tagged a new Go release: go1.Go 1 is a major release of Go that will be stable in the long term.
It is intended that programs written for Go 1 will continue to compile
and run correctly, unchanged, under future versions of Go 1.The Go 1 release notes list the significant changes since the last
release and explain how to update your code:
http://golang.org/doc/go1.htmlTo learn about the future of Go 1, read the Go 1 compatibility document:
http://golang.org/doc/go1compat.htmlGo 1 is available as binary distributions for the
FreeBSD, Linux, Mac OS X, and Windows operating systems.
To install a binary distribution, follow these instructions:
http://golang.org/doc/installIf you prefer to build from source, follow these instructions:
http://golang.org/doc/install/sourceThe Go team would like to thank all our contributors from the open
source community. We could not have done it without their help.
See the full list of contributors here: http://golang.org/CONTRIBUTORSWe also thank our users. We hope you enjoy Go 1.
Have fun. (And tell your friends! ;-)
Andrew