Release v0.2.7(CloneIndragie)

Highlights:

• Fixed getting with Go1.5. This issue was raised by @rakyll in #265. What happened was that initially Go tip was a little unstable and tripped out whenever internal packages were used. Reports were made to the Google Go API client googleapis/google-api-go-client#87, and it was a known at the mother ship golang/go#11307. The issue was fixed and all that propagated back, however drive was using my curated clone of the Google Go API because I have previously encountered issues with instability. However, the drive.v2 api is now imported using the official Google Go API switched that over in 8d2cc60.
• Fixed up the coerced mime type for Google Sheeets. This was raised in issue #289. It was addressed by PR #290. In this PR the ability to coerce a script to a Google AppScript was introduced. The mimeType was originally being incorrectly resolved to

- "application/vnd.google-apps.sheet"
// yet it is actually
+ "application/vnd.google-apps.spreadsheet"

• Fixed up drive about with no sub command arguments. This was raised in issue #294. Basically it was expecting arguments --features, --files, --quota. This was addressed by PR #295. Now whenever it is invoked without arguments it gives output as a combination of all its sub commands.
• documented option mime-short-key. This was raised by @canpolat in issue #298. The lack of this documented option was confusing to users and was addressed also by @canpolat in PR #299.
• a question was answered concerning drive being able to interact with the new Google Photos. Yes, it can interact with Google Photos. This was raised by @derekxgl in issue #301. The solution to this question was provided by @jonbrock with the following instructions in #301.

You can create a Google Photos folder in your Google Drive now, and then
use drive to manipulate the photos. To set it up, go to drive.google.com,
open settings, scroll down and enable the "Create a Google Photos folder" option.
Once it's created you can rename the folder (if you want) and it continues to work.

• More diagnostic information is provided during pulls and pushes in case of any failures. Previously ignored errors caused users to think they were spurious modifications. This was raised by @pefoley2 in #304. This issue was addressed by PR #305.
• With the need to inform the user of errors encountered ie in PRhttps://github.com//pull/305 , this actually uncovered another bug in #306. This issue was raised by @pefoley2. Basically what was happening was that due to desktop entries being created instead of empty files on every pull of Google Docs + Sheets. However the logic of these being the equivalent for their non *.desktop suffixed files was not working hence always requested downloads. This issue was fixed by PR #307.
• listing of commands and subcommands when -h or --help was passed in now sorted and no longer random. This issue was raised by @da-x. This issue was out of the control of drive. However it was from one of the packages that I have control over so I was able to fix this in PR odeke-em/command#3.
• drive-gen always revert gen/generated.go after binary generation: This issue was raised in #310 and became a nuisance every time a user ran go get github.com/odeke-em/drive/drive-gen && drive-gen to bundle build information into the binary, always leaving gen/generated.go modified. This was fixed by PR #312.
• bundling BuildTime into the binary: It is useful for a user to know when a binary was built. This issue was raised in #311 and addressed by #312. Originally

- $ drive version
- drive version: 0.2.6
- Commit Hash: 'c9fbf001df5eba932ad1f38bcdbf40fc5c5fa6e0'
- Go Version: go1.4.2
- OS: darwin/amd64

// Now
+ drive version: 0.2.7
+ Commit Hash: '9162e93e83571286b4c400e3dcc8cad88f5a172f'
+ Go Version: devel +bd1efd5 Fri Jul 31 16:11:21 2015 +0000
+ OS: darwin/amd64
+ BuildTime: 2015-07-31 20:57:51.548074555 -0600 MDT

• Fixed pull option --export. This issue was raised in #313. It was introduced in commit 787e7f0. It was addressed by PR #314.

This release includes a whole bunch of fixes mostly and in this time we've encountered way more interaction with new users. Also new ideas are coming through, and more users are fixing problems for others and answering questions.
This is great news and it shows adoption plus more experimentation.
A quick shoutout to @indragiek who is also a contributor -- congrats on completing a successful 3 month code workout. In the words of the wise person you know, "Let's clone more Indragies!".

Thank you very much to all the contributors, issue raisers, users, observers!