Tuesday, February 28, 2012

App Engine 1.6.3 Released

Our second release of this year will have you leaping into action to start using the new features immediately. What could be more exciting than a feature to support A/B testing on your app? Or DKIM signing when you send email from your Google Apps domain? This release has plenty of exciting changes to keep you busy on your extra day this year.

1.6.3 Platform Changes:

  • A new Experimental feature called Traffic Splitting lets you send a percentage of your traffic to different versions of your app. Traffic can be split based either on IP or on cookie.
  • When an email is sent either from a user of a Google Apps domain from a request originating on that domain, or from an app administrator with an account on a Google Apps domain, a DKIM signature will be automatically applied to the email.
1.6.3 Admin Console Changes
  • Billed applications can now specify the amount of storage used for logs and the duration of time these logs are stored (default is 90 days) as well as view the currently stored amount in the Admin Console. The first gigabyte of logs storage is free and additional storage will be charged at $0.24/G/month. These settings are now available, but additional storage will not be charged for at least 4 weeks, at that point any logs beyond the configured amount will be deleted.
  • You can now manually shut down an instance in the Instances view of the Admin Console.
  • The Logs Viewer for each request now provides a link to the instance that served that request (as long as the instance is still active).
These are just some of the highlights in 1.6.3. As usual, our release notes for Python® and Java® contain the full list of all the new features and bug fixes, so be sure to check out all the exciting things we’ve been working hard to release this past month.


5 comments:

geltabs said...

awesome work! congrats

Jonathan Chen said...

Since the upgrade, deployments don't succeed anymore.

Mihai said...

great update ! However I think you should monitor/restrict the email service otherwise the abuse will make DKIM useless as the SPF too. Amazon SES did a good job there.

mads said...

Is there any reason you've put django 1.3 in the python 2.7 runtime, and not 1.3.1?

1.3 has a couple of security vulnerabilities you should be aware of.

patience2 said...

This is great,nice work put together