A friendly heads-up: Deletion of Go1.4-dependent code in x/tools repo
359 views
Skip to first unread message
Robert Griesemer
unread,
Feb 29, 2016, 2:54:21 PM2/29/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to golang-...@googlegroups.com
If you don't depend on x/tools packages building against Go 1.4 you can stop reading now.
Go 1.6 was released on February 17, 2016. One month later, starting March17, golang.org/x/toolsrepository will no longer build with Go 1.4, and we will delete the followinggolang.org/x/toolspackages:
After March 17, you must use Go version 1.5 or later to build x/tools packages depending on go/types, or maintain your own "vendored" copy of the current contents of thegolang.org/x/toolsrepository.
Because we knew this deletion would affect use cases such as the one you mentioned, we waited an extra six months (one release cycle) to give users additional time to update, and we pre-announced the change in October (see Robert's original email for the link). That's a significant grace period with significant advance notice.
We can't keep the code running indefinitely. People who need to keep running Go 1.4 can in the worst case make their own copy of the code, but we'd also love to hear from them about why they're still on Go 1.4 so that we can address those reasons.
Thanks.
Russ
Russ Cox
unread,
Mar 1, 2016, 10:25:41 AM3/1/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Konstantin Shaposhnikov, Robert Griesemer, golang-dev
[bcc golang-announce to move future replies off, sorry]