News for hackers. Stuff that matters.
Re:Introducing the Rails API Project by viseztrance on Thursday November 22, 2012 @01:30PM (#4819601)
A few days ago I found myself getting a rather strange git error while running bundle after upgrading to the latest ruby. Turns out the active record serializer gem was moved just hours earlier to this rails-api location without any reason or notice. It was referenced by a git revision, because we needed the latest changes and it was also encouraged in the readme (as it still is now).

My issue with all this is that we already had tagged revisions in our application and this basically broke our older builds on which we actually relied on should things go wrong (the application is a rails engine).

So I think it would had been nice if this was announced earlier.

Re:Introducing the Rails API Project by steveklabnik2 on Thursday November 22, 2012 @01:49PM (#4819659)
So sorry about this. I was travelling back from Europe, and we had to coordinate between everyone who owned the various gems, so there was a bit of overlap there.

I hope to not be encouraging people to use HEAD soon.

Re:Introducing the Rails API Project by viseztrance on Thursday November 22, 2012 @01:56PM (#4819680)
It's ok. I think we should had fork the repo and reference that in the first place.