Go 1.1 design freeze

2,248 views
Skip to first unread message

Russ Cox

unread,
Jan 31, 2013, 11:18:14 PM1/31/13
to golang-dev
We were pretty much already there, but just to make it official: we're now in the Go 1.1 design freeze, meaning that new features or changes requested after today will be postponed to after Go 1.1. I also changed the default label for newly created issues to Go1.1Maybe.

This isn't an implementation freeze: there's plenty left in the issue tracker that we have left to do. As of right now there are 215 open Go 1.1 issues. (The page at http://swtch.com/~rsc/go11.html is stalled right now but should be updating again in about 24 hours.) 

Russ

minux

unread,
Mar 6, 2013, 5:09:39 AM3/6/13
to Russ Cox, golang-dev
On Fri, Feb 1, 2013 at 12:18 PM, Russ Cox <r...@golang.org> wrote:
We were pretty much already there, but just to make it official: we're now in the Go 1.1 design freeze, meaning that new features or changes requested after today will be postponed to after Go 1.1. I also changed the default label for newly created issues to Go1.1Maybe.
it seems the default label changes to Go1.1 somehow?
this newly created issue is labeled Go1.1: https://code.google.com/p/go/issues/detail?id=4988 

Russ Cox

unread,
Mar 6, 2013, 11:36:36 AM3/6/13
to minux, golang-dev
On Wed, Mar 6, 2013 at 2:09 AM, minux <minu...@gmail.com> wrote:
it seems the default label changes to Go1.1 somehow?
this newly created issue is labeled Go1.1: https://code.google.com/p/go/issues/detail?id=4988 

Either the issue started with the compilerbug template, which was still defaulting to Go1.1 but is now Go1.1Maybe, or the person who filed it marked it Go1.1 by hand (maybe that's not possible).

Russ

Rob Pike

unread,
Apr 3, 2013, 1:03:25 AM4/3/13
to golang-dev
We're close to ready to try a candidate release. Naturally, the looming release brings urgency to get all those "I want it" changes in before the flag falls.  Well, it's falling now. To keep the focus on getting that put together, and mixing metaphors even more, the freeze is going colder.

Please, no new code or features or suggestions or language changes or performance improvements unless they directly address the tasks that need to be done for Go 1.1 as listed here:


Even that page is optimistic about what will actually make the cut.

-rob

Reply all
Reply to author
Forward
0 new messages