While it asks for a signup it's just looking for a valid unique email so you can use pretty much anything. The matching stage is the only point where emails are actually dispatched
Should have said while it does ask for an email during signup it doesn't require any activation and will work so long as the email address is in a valid format
I might be wrong but would the trick maybe be to break it down bit by bit, so for instance break off your existing file upload stuff and replace it with CarrierWave or something different. I don't know what your codebase is like but doing it that way should in theory make it more copable to slowly tick it up to rails 3+
Gotcha, there's also some information on migrating to paperclip[1] which might suit and I'm sure someone will have done similar for CarrierWave. Of course none of that helps with being short staffed.
He said he planned to switch to the Xperia T, but I guess he will want to leave something at least workable for the S3 before that.
EDIT: not sure about the current state of things, seems that this is a translation from an interview that happened several months ago, which explains why the Xperia T wasn't out yet.
Yeah, I've kept a close eye on this since I own an S3 and run CM and he's definitely still working on it from what I've seen. That might be related to Samsung saying they'd be more open going forward though
While it asks for a signup it's just looking for a valid unique email so you can use pretty much anything. The matching stage is the only point where emails are actually dispatched