{"issue":{"created_at":"2011-12-13T17:39:53Z","state":"closed","updated_at":"2011-12-15T01:19:00Z","user":{"gravatar_id":"f00c0c6636de02f40334d0fbd98a99f4","id":1226596,"url":"https://api.github.com/users/bclark-ethos","login":"bclark-ethos","avatar_url":"https://secure.gravatar.com/avatar/f00c0c6636de02f40334d0fbd98a99f4?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":4,"body":"Commit fec35c3af6b143b0b34aa93e009c0dbe1e50a20b & 06279837f6c771b52d77cd34b3f4e89b8d0a05f8 breaks default configuration of spree. While developing with a Gemfile of:\r\n\r\ngem 'spree'\r\ngem 'spree_static_content', :git => 'git://github.com/spree/spree_static_content.git'\r\n\r\nThe latest commit assumes that spree is also running off the HEAD from the spree/spree repository. This is bad seeing as the gem on rubygems.org is old.","assignee":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"id":2540270,"labels":[],"number":27,"title":"fec35c3af6 & 06279837f6 Breaks spree","html_url":"https://github.com/spree/spree_static_content/issues/27","closed_at":"2011-12-13T17:43:42Z","url":"https://api.github.com/repos/spree/spree_static_content/issues/27","milestone":null},"action":"created","comment":{"created_at":"2011-12-15T01:19:00Z","updated_at":"2011-12-15T01:19:00Z","user":{"gravatar_id":"9a2a53db8e9b4476038c94a64b32833f","id":2687,"url":"https://api.github.com/users/radar","login":"radar","avatar_url":"https://secure.gravatar.com/avatar/9a2a53db8e9b4476038c94a64b32833f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"We're aiming to get a 1.0RC out around Christmas time, with the full-fledged release being released before SpreeConf (Mid February).","id":3155245,"url":"https://api.github.com/repos/spree/spree_static_content/issues/comments/3155245"}}