Go 1.4 work begins

1,445 views
Skip to first unread message

Russ Cox

unread,
Jun 10, 2014, 7:59:00 PM6/10/14
to golang-dev
We are still shaking out the last few bugs in Go 1.3, but that is being done on the release branch and is mostly a matter of waiting at this point.

It is now okay to send CLs for Go 1.4 for all of the tree except the runtime and compilers.

We have a few large changes to the runtime and compilers pending; we want to get those submitted before we open to more general changes.

Thanks.
Russ



andrewc...@gmail.com

unread,
Jun 10, 2014, 9:51:04 PM6/10/14
to golan...@googlegroups.com
Will the toolchains that are being used in 1.4 to translate C to Go be public and part of the build process, or will it be kept internal to google and then the Go code checked in as large chunks?

Sorry if this is the wrong thread to ask.

Anthony Martin

unread,
Jun 11, 2014, 3:15:43 AM6/11/14
to andrewc...@gmail.com, golan...@googlegroups.com
andrewc...@gmail.com once said:
> Will the toolchains that are being used in 1.4 to translate C to Go be
> public and part of the build process, or will it be kept internal to google
> and then the Go code checked in as large chunks?

% go get code.google.com/p/rsc/c2go

Anthony

Aram Hăvărneanu

unread,
Jun 11, 2014, 4:24:27 AM6/11/14
to Anthony Martin, andrewc...@gmail.com, golang-dev
> % go get code.google.com/p/rsc/c2go

Seems to be missing some files, main.go is // +build ignore and
imports code.google.com/p/rsc/c2go, so presumably there should be
more files from a package there.

--
Aram Hăvărneanu

Russ Cox

unread,
Jun 11, 2014, 10:49:56 AM6/11/14
to Aram Hăvărneanu, Anthony Martin, andrewc...@gmail.com, golang-dev
Yes, well, it's not done yet.

Russ 

Dmitry Vyukov

unread,
Jun 11, 2014, 10:59:12 AM6/11/14
to Russ Cox, Keith Randall, golang-dev
On Wed, Jun 11, 2014 at 3:58 AM, Russ Cox <r...@golang.org> wrote:
> We are still shaking out the last few bugs in Go 1.3, but that is being done
> on the release branch and is mostly a matter of waiting at this point.
>
> It is now okay to send CLs for Go 1.4 for all of the tree except the runtime
> and compilers.

Is it the whole runtime? Or only goc files (C code running on user goroutines)?
Can I ask to prioritize chan.goc?

Sebastien Douche

unread,
Jul 21, 2014, 4:34:37 PM7/21/14
to Russ Cox, golang-dev
On Wed, Jun 11, 2014 at 1:58 AM, Russ Cox <r...@golang.org> wrote:
> We are still shaking out the last few bugs in Go 1.3, but that is being done
> on the release branch and is mostly a matter of waiting at this point.

Hi,
40 days later, no release. Seems not a good idea to follows 2 goals in
the same time.


--
Sebastien Douche <sdo...@gmail.com>
Twitter: @sdouche / G+: +sdouche

Ian Lance Taylor

unread,
Jul 21, 2014, 4:35:54 PM7/21/14
to Sebastien Douche, Russ Cox, golang-dev


On Jul 21, 2014 4:34 PM, "Sebastien Douche" <sdo...@gmail.com> wrote:
>
> On Wed, Jun 11, 2014 at 1:58 AM, Russ Cox <r...@golang.org> wrote:
> > We are still shaking out the last few bugs in Go 1.3, but that is being done
> > on the release branch and is mostly a matter of waiting at this point.
>
> Hi,
> 40 days later, no release. Seems not a good idea to follows 2 goals in
> the same time.

There was a release.  Did you miss it?

Ian

> --
> You received this message because you are subscribed to the Google Groups "golang-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Sebastien Douche

unread,
Jul 22, 2014, 2:49:07 AM7/22/14
to Russ Cox, golang-dev
On Mon, Jul 21, 2014 at 10:33 PM, Sebastien Douche <sdo...@gmail.com> wrote:
> 40 days later, no release. Seems not a good idea to follows 2 goals in
> the same time.

Some times you are ridiculous. Kill me :(.
Reply all
Reply to author
Forward
0 new messages