Bump travis-core
Merge branch 'master' of github.com:travis-ci/travis-api
Use ruby 2.0.0
Merge branch 'master' of github.com:travis-ci/travis-api

Choose remote

Conflicts:
	Gemfile.lock
update travis-core
Merge branch 'master' of github.com:travis-ci/travis-api
WIP: Atom feed for /repos/:owner_name/:name/builds

See travis-ci/travis-core#82

TODO: Link to indivisual build.
TODO: Add specs.
TODO: Review `#apply?`
Use here-doc for Atom feed template

Rather than unnaturally re-reading __FILE__ and splitting,
use a here-doc to clarify the intent.
(Should also consider splitting it to a file.)
Construct build result URL from parts

Currently, there is no easy way to grab this information from
the Build model.
So we need to construct it from various parts at our disposal.
Eradicate @builds

Unclear if ivar is beneficial here.
Add integration specs for Atom feed

These rudimentary specs do not test the correctness of
the Atom feed format.
Prefer JSON to Atom feed

We should not break the current behavior when the client sends
`Accept: */*` HTTP header.
Set update element to RFC3339 format

This is required by the RFC.

http://tools.ietf.org/html/rfc4287#section-3.3
Encode commit message

So that HTML/XML tags in messages don't break the feed.
Accept `.atom` extension

And return Atom feed for builds.
Specs look different, because it needs to explicitly handle the common
case where the client sends `Accept: */*`.
Atom feed's date should conform to RFC 3339.
Tweak feed and entry's IDs
Merge pull request #96 from BanzaiMan/gh82_atom_feed

Implement Atom feed
a bundle update of sorts
update the gemspec for profit!