3 ms·
I sent out the notification from my @heroku.com email, and not from an auto mailer. We have the capability and do send out system wide emails, but I wanted to p
by thinkbohemian 14y ago
I sent out the notification from my @heroku.com email, and not from an auto mailer. We have the capability and do send out system wide emails, but I wanted to personally field any questions or concerns directly.
No one has indicated that they cannot migrate their app at all. A few have told me that they are not the original developers, but we haven't run into that exact situation. We do have http://partners.heroku.com http://partners.heroku.com available for contract if someone truly was non-technical. Even then, the experience of hiring contractors for a few hours to work on an app that has been running for the last 4+ years shouldn't be too bad.
Even in microsoft's case, longer support lifetimes still don't mean infinite support lifetimes. People still need to migrate and un-necessarily prolonging the migration can make it much-much harder.
To read up more on our deprecation and sunsetting policies check out my last blog post: http://blog.heroku.com/archives/2012/9/24/sunsetting-and-deprecation/ http://blog.heroku.com/archives/2012/9/24/sunsetting-and-dep...
- DASD 14y agoThanks for taking the time to respond. The ability to shutoff technology/features is definitely a plus when you are running a PAAS. I've still got clients that are running large lab operations on NT and also some clients still running extremely old versions of RPG. None have found the incentive to rewrite the software along the way.