From 33bf5888850f0107a15c013dcd0db0f5b558241b Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 21 Aug 2016 12:23:03 -0700 Subject: [PATCH 1/7] Add blog post "GopherJS 1.7-1 is released". Helps gopherjs/gopherjs#500. --- ...2016-08-21-gopherjs-1.7-1-release.markdown | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 _posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown diff --git a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown new file mode 100644 index 00000000..bce9ecd5 --- /dev/null +++ b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown @@ -0,0 +1,24 @@ +--- +layout: post +title: "GopherJS 1.7-1 is released" +date: 2016-08-21 +author: Dmitri Shuralyov +--- + +Hello gophers, + +Today, we are happy to make two announcements for GopherJS. First, GopherJS now [officially supports Go 1.7](https://github.com/gopherjs/gopherjs/issues/475), which is the current stable release of Go that came out recently. Second, GopherJS has its first named version attached to it, and we're calling it GopherJS 1.7-1. This makes it possible to have a release history tracking major changes and additions between versions. + +The support for Go 1.7 means that GopherJS 1.7-1 requires Go 1.7 and no longer works with Go 1.6. It's highly recommended to be using the latest version of Go and GopherJS, but if you cannot update from Go 1.6 right away, you should continue to use GopherJS on the [`go1.6` branch](https://github.com/gopherjs/gopherjs/commits/go1.6). + +GopherJS 1.7-1 continues to support nearly everything of the [Go language specification](https://golang.org/ref/spec), including goroutines. Please consult the [package compatibility table](https://github.com/gopherjs/gopherjs/blob/master/doc/packages.md) to see which standard library packages are supported. Everything from the previous Go 1.6 version is still supported, as are many additions to Go 1.7, but there are some exceptions. For example, the new [`reflect.StructOf` function](https://godoc.org/reflect#StructOf) is not yet supported, but [issue #499](https://github.com/gopherjs/gopherjs/issues/499) tracks its implementation status. If you run into any bugs or discrepancies with what the compatibility table says, please [file an issue](https://github.com/gopherjs/gopherjs/issues). + +Installation or upgrade instructions remain the same, even though GopherJS has a version number now. To get the latest official stable release, please follow the instructions at https://github.com/gopherjs/gopherjs#installation-and-usage. You can confirm that you have the right version if `gopherjs version` prints `GopherJS 1.7-1`. + +Over the last few years, GopherJS has become increasingly complete and stable. Support for many advanced features of the Go language spec, such as goroutines, channels, and select statements, was added over time. More and more of the viable standard library packages would have all their tests pass and become officially supported. Many bugs were reported, investigated and fixed. GopherJS has become quite stable and is used by many for a broad range of projects. + +However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would be aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and that you can get started with it today. + +In closing, we would like to thank every contributor to this project for helping making this release of GopherJS possible. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support, and many people have contributed code, reported/investigated/helped reproduce bugs, created libraries and wrappers for various browser APIs. Everyone's effort helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! + +Happy surfing with Go and GopherJS! From c81a8f3341dfa472be704e4c3214829e7762230b Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 21 Aug 2016 12:27:37 -0700 Subject: [PATCH 2/7] Be more specific, relevant to theme of post. --- _posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown index bce9ecd5..612f9a18 100644 --- a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown +++ b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown @@ -21,4 +21,4 @@ However, many of those improvements to GopherJS were done quietly and internally In closing, we would like to thank every contributor to this project for helping making this release of GopherJS possible. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support, and many people have contributed code, reported/investigated/helped reproduce bugs, created libraries and wrappers for various browser APIs. Everyone's effort helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! -Happy surfing with Go and GopherJS! +Happy surfing with Go 1.7 and GopherJS 1.7-1! From a4ae1dee0a86f230f4b7e7af14733f7b1832397a Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 21 Aug 2016 14:08:22 -0700 Subject: [PATCH 3/7] Also thank the Go team. Without the Go team creating Go and releasing Go 1.7, GopherJS 1.7-1 would not be possible. It's also more consistent with the sign off phrase "Happy surfing with Go 1.7 and GopherJS 1.7-1!" --- _posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown index 612f9a18..0e7498ba 100644 --- a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown +++ b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown @@ -19,6 +19,6 @@ Over the last few years, GopherJS has become increasingly complete and stable. S However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would be aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and that you can get started with it today. -In closing, we would like to thank every contributor to this project for helping making this release of GopherJS possible. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support, and many people have contributed code, reported/investigated/helped reproduce bugs, created libraries and wrappers for various browser APIs. Everyone's effort helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! +In closing, we would like to thank everyone who contributed to this release of GopherJS. The Go team created and released Go 1.7. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support. Many people have contributed code and bug fixes, reported/investigated/helped reproduce issues, created libraries and wrappers for various browser APIs. Everyone's effort helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! Happy surfing with Go 1.7 and GopherJS 1.7-1! From fd872158d2df107d32f06d1fa29ec1e02f04ed65 Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 21 Aug 2016 15:45:51 -0700 Subject: [PATCH 4/7] Apply copy edits based on review. Remove link from first paragraph because it dilutes the message and is unhelpful in the context. Rewrite a paragraph to have a more consistent past tense, and finish it with the present. Minor improvements to other sentences. --- _posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown index 0e7498ba..047fd3cb 100644 --- a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown +++ b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown @@ -7,7 +7,7 @@ author: Dmitri Shuralyov Hello gophers, -Today, we are happy to make two announcements for GopherJS. First, GopherJS now [officially supports Go 1.7](https://github.com/gopherjs/gopherjs/issues/475), which is the current stable release of Go that came out recently. Second, GopherJS has its first named version attached to it, and we're calling it GopherJS 1.7-1. This makes it possible to have a release history tracking major changes and additions between versions. +Today, we are happy to make two announcements for GopherJS. First, GopherJS now officially supports Go 1.7, which is the current stable release of Go that came out recently. Second, GopherJS has its first named version attached to it, and we're calling it GopherJS 1.7-1. This makes it possible to have a release history tracking major changes and additions between versions. The support for Go 1.7 means that GopherJS 1.7-1 requires Go 1.7 and no longer works with Go 1.6. It's highly recommended to be using the latest version of Go and GopherJS, but if you cannot update from Go 1.6 right away, you should continue to use GopherJS on the [`go1.6` branch](https://github.com/gopherjs/gopherjs/commits/go1.6). @@ -15,10 +15,10 @@ GopherJS 1.7-1 continues to support nearly everything of the [Go language specif Installation or upgrade instructions remain the same, even though GopherJS has a version number now. To get the latest official stable release, please follow the instructions at https://github.com/gopherjs/gopherjs#installation-and-usage. You can confirm that you have the right version if `gopherjs version` prints `GopherJS 1.7-1`. -Over the last few years, GopherJS has become increasingly complete and stable. Support for many advanced features of the Go language spec, such as goroutines, channels, and select statements, was added over time. More and more of the viable standard library packages would have all their tests pass and become officially supported. Many bugs were reported, investigated and fixed. GopherJS has become quite stable and is used by many for a broad range of projects. +Over the last few years, GopherJS has become increasingly complete and stable. Many advanced features of the Go language spec were implemented (such as goroutines, channels, and select statements). More and more of the viable standard library packages had all their tests pass and became officially supported. Many bugs were reported, investigated, and fixed. Today, it is used by many people for a broad range of projects. -However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would be aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and that you can get started with it today. +However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would be aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and the fact that you can get started with it today. -In closing, we would like to thank everyone who contributed to this release of GopherJS. The Go team created and released Go 1.7. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support. Many people have contributed code and bug fixes, reported/investigated/helped reproduce issues, created libraries and wrappers for various browser APIs. Everyone's effort helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! +In closing, we would like to thank everyone who contributed to this release of GopherJS. The Go team created and released Go 1.7. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support. Many people have contributed code and bug fixes, reported/investigated/helped reproduce issues, created libraries and wrappers for various browser APIs. Everyone's effort has helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! Happy surfing with Go 1.7 and GopherJS 1.7-1! From 5d68a46c56fc01fcd33ddad18b67a0701e7650ad Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 21 Aug 2016 15:50:37 -0700 Subject: [PATCH 5/7] "would be aware" -> "would become aware" Because the improvements were done quietly, fewer people would _become_ aware of those improvements. This seems to fit in slightly better. --- _posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown index 047fd3cb..93ca07c2 100644 --- a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown +++ b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown @@ -17,7 +17,7 @@ Installation or upgrade instructions remain the same, even though GopherJS has a Over the last few years, GopherJS has become increasingly complete and stable. Many advanced features of the Go language spec were implemented (such as goroutines, channels, and select statements). More and more of the viable standard library packages had all their tests pass and became officially supported. Many bugs were reported, investigated, and fixed. Today, it is used by many people for a broad range of projects. -However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would be aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and the fact that you can get started with it today. +However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would become aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and the fact that you can get started with it today. In closing, we would like to thank everyone who contributed to this release of GopherJS. The Go team created and released Go 1.7. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support. Many people have contributed code and bug fixes, reported/investigated/helped reproduce issues, created libraries and wrappers for various browser APIs. Everyone's effort has helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! From 43f2ed168f54eb70ff85a20c1a6771d6be9818f4 Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 21 Aug 2016 17:20:40 -0700 Subject: [PATCH 6/7] Add short paragraph mentioning next steps to get started. For people new to GopherJS who may see this post, this gives them some actionable next steps to perform. It gives a little more meaning to the sign off phrase. It also indirectly shows that the GopherJS playground has been updated for Go 1.7/GopherJS 1.7-1. --- _posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown index 93ca07c2..979f2997 100644 --- a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown +++ b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown @@ -21,4 +21,9 @@ However, many of those improvements to GopherJS were done quietly and internally In closing, we would like to thank everyone who contributed to this release of GopherJS. The Go team created and released Go 1.7. Richard Musiol created and implemented the core parts of GopherJS and Go 1.7 support. Many people have contributed code and bug fixes, reported/investigated/helped reproduce issues, created libraries and wrappers for various browser APIs. Everyone's effort has helped get GopherJS to where it is today, giving us the opportunity to write front-end code in Go which will run in all modern browsers. See [list of code contributors](https://github.com/gopherjs/gopherjs/graphs/contributors) and [list of closed issues](https://github.com/gopherjs/gopherjs/issues?q=is%3Aissue+is%3Aclosed). We welcome all help; if you'd like to get involved, see the [community section](https://github.com/gopherjs/gopherjs#community). If you have a good experience with GopherJS, tell your fellow gophers about it! +If you'd like to get started with GopherJS, here are some next steps you can take: + +- Try it right now in your browser with the [GopherJS playground](http://www.gopherjs.org/playground/#/-MweO3kLBk). +- Begin creating your web app using the [gopherpen template project](https://github.com/gopherjs/gopherpen#readme) as a starting point. + Happy surfing with Go 1.7 and GopherJS 1.7-1! From d8500295af3f88bd88d71576f70292222de50a68 Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 21 Aug 2016 17:24:26 -0700 Subject: [PATCH 7/7] Fix bug. It's unhelpful to use slang/short version of spec. Use the proper word. It's also inconsistent with the paragraph above, where the full word was used. --- _posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown index 979f2997..a782f151 100644 --- a/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown +++ b/_posts/blog/2016-08-21-gopherjs-1.7-1-release.markdown @@ -15,7 +15,7 @@ GopherJS 1.7-1 continues to support nearly everything of the [Go language specif Installation or upgrade instructions remain the same, even though GopherJS has a version number now. To get the latest official stable release, please follow the instructions at https://github.com/gopherjs/gopherjs#installation-and-usage. You can confirm that you have the right version if `gopherjs version` prints `GopherJS 1.7-1`. -Over the last few years, GopherJS has become increasingly complete and stable. Many advanced features of the Go language spec were implemented (such as goroutines, channels, and select statements). More and more of the viable standard library packages had all their tests pass and became officially supported. Many bugs were reported, investigated, and fixed. Today, it is used by many people for a broad range of projects. +Over the last few years, GopherJS has become increasingly complete and stable. Many advanced features of the Go language specification were implemented (such as goroutines, channels, and select statements). More and more of the viable standard library packages had all their tests pass and became officially supported. Many bugs were reported, investigated, and fixed. Today, it is used by many people for a broad range of projects. However, many of those improvements to GopherJS were done quietly and internally, so only developers and people who follow the project very closely would become aware. Without a version number and release history, it's harder for newcomers or people waiting for a stable release to have insight on the readiness state of GopherJS. With this version number and future release history, we hope to better communicate the maturity level of GopherJS and the fact that you can get started with it today.