aboutsummaryrefslogtreecommitdiff
path: root/content/appengine-ga.article
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2020-03-15 15:50:36 -0400
committerRuss Cox <rsc@golang.org>2020-03-17 20:58:46 +0000
commit972d42d925e6cae3f8eebd9b21d445e06c2eb386 (patch)
tree737af27f0d49318b612efec874b1d1328c699d1a /content/appengine-ga.article
parentfaf1e2da2d911edc717993e8edb24fe88f99b2b5 (diff)
content: rename articles to reinforce convention of short URLs
The Go blog started out on Blogger (http://web.archive.org/web/20100325005843/http://blog.golang.org/). Later, we moved to the current self-hosted blog server with extra Go-specific functionality like playground snippets. The old Blogger posts have very long URLs that Blogger chose for us, such as "go-programming-language-turns-two" or "two-go-talks-lexical-scanning-in-go-and", predating the convention of giving posts shorter, more share-friendly, typeable names. The conversion of the old Blogger posts also predated the convention of putting supporting files in a subdirectory. The result is that although we've established new conventions, you wouldn't know by listing the directory - the old Blogger content presents a conflicting picture. This commit renames the posts with very long names to have shorter, more share-friendly names, and it moves all supporting files to subdirectories. It also adds a README documenting the conventions. For example, blog.golang.org/go-programming-language-turns-two is now blog.golang.org/2years, matching our more recent birthday post URLs, and its supporting files are moved to the new 2years/ directory. The old URLs redirect to the new ones. Change-Id: I9f46a790c2c8fab8459aeda73d4e3d2efc86d88f Reviewed-on: https://go-review.googlesource.com/c/blog/+/223599 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Andrew Bonventre <andybons@golang.org>
Diffstat (limited to 'content/appengine-ga.article')
1 files changed, 36 insertions, 0 deletions
diff --git a/content/appengine-ga.article b/content/appengine-ga.article
new file mode 100644
index 0000000..964efc1
--- /dev/null
+++ b/content/appengine-ga.article
@@ -0,0 +1,36 @@
+# Go for App Engine is now generally available
+21 Jul 2011
+Tags: appengine, release
+Summary: You can use Go on App Engine now!
+OldURL: /go-for-app-engine-is-now-generally
+
+Andrew Gerrand
+
+##
+
+The Go and App Engine teams are excited to announce that the Go runtime
+for App Engine is now generally available.
+This means you can take that Go app you've been working on (or meaning to
+work on) and deploy it to App Engine right now with the new [1.5.2 SDK](http://code.google.com/appengine/downloads.html).
+
+Since we announced the Go runtime at Google I/O we have continued to [improve and extend](http://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes)
+Go support for the App Engine APIs and have added the Channels API.
+The Go Datastore API now supports transactions and ancestor queries, too.
+See the [Go App Engine documentation](https://code.google.com/appengine/docs/go/)
+for all the details.
+
+For those who have been using the Go SDK already,
+please note that the 1.5.2 release introduces `api_version` 2.
+This is because the new SDK is based on Go `release.r58.1` (the current
+stable version of Go) and is not backwards compatible with the previous release.
+Existing apps may require changes as per the [r58 release notes](https://golang.org/doc/devel/release.html#r58).
+Once you've updated your code, you should redeploy your app with the line
+`api_version: 2` in its `app.yaml` file.
+Apps written against `api_version` 1 will stop working after the 18th of August.
+
+Finally, we owe a huge thanks to our trusted testers and their many bug reports.
+Their help was invaluable in reaching this important milestone.
+
+_The fastest way to get started with Go on App Engine is with the_ [_Getting Started guide_](http://code.google.com/appengine/docs/go/gettingstarted/).
+
+_Note that the Go runtime is still considered experimental; it is not as well-supported as the Python and Java runtimes._