Maybe add a warning message on deploy?

On Tue, Sep 3, 2013 at 4:39 PM, Robbie Thng <rob...@heroku.com> wrote:

> That's a good point, I don't think we have a good way of notifying of this
> right now.
>
> Their add-on page isn't available for consumption but other than notifying
> users by email we don't really have a way of conveying this across the
> platform. We're mostly relying on users checking their email but that's
> understandably hard for orgs.
>
>
> On Fri, Aug 30, 2013 at 5:09 AM, Daniel Doubrovkine <dbl...@dblock.org>wrote:
>
>> Got it. We have a shared IT account that subscribes to those, took a
>> while to dig it up. Would be nice if everything online reflected this
>> reality.
>>
>>
>> On Tue, Aug 27, 2013 at 5:31 PM, Robbie <rob...@heroku.com> wrote:
>>
>>> Hi Daniel,
>>>
>>> We sent this out to users that we identified as having Couchbase
>>> Memcache add-ons. Are you a user of that add-on and did you not receive the
>>> notice?
>>>
>>> R
>>>
>>>
>>> On Tuesday, August 27, 2013 2:28:15 PM UTC-7, dB. wrote:
>>>
>>>> For the life of me I cannot find that announcement. Where did you read
>>>> that the date is October 31st? Thanks.
>>>>
>>>> On Mon, Aug 26, 2013 at 10:04 AM, jonathan <jonathan...@gmail.com>wrote:
>>>>
>>>>> As many of you know, Heroku is deprecating their memcache addon in
>>>>> favor of the Memcachier service. Customers are required to switch to the
>>>>> new servers by Oct 31.
>>>>>
>>>>> For high traffic sites, transitioning to a cold memcache server can be
>>>>> difficult. I threw together a ruby gem that will allow you to run both 
>>>>> sets
>>>>> of memcache servers in production for a transition period, while your new
>>>>> memcache servers warm up.
>>>>>
>>>>> https://github.com/jbaudanza/**cache_migration<https://github.com/jbaudanza/cache_migration>
>>>>>
>>>>> Let me know if you have any questions. I hope you find this helpful.
>>>>>
>>>>> --
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Heroku" group.
>>>>>
>>>>> To unsubscribe from this group, send email to
>>>>> heroku+un...@**googlegroups.com
>>>>>
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/**group/heroku?hl=en_US?hl=en<http://groups.google.com/group/heroku?hl=en_US?hl=en>
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Heroku Community" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to heroku+un...@**googlegroups.com.
>>>>>
>>>>> For more options, visit 
>>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>>> .
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> dB. | Moscow - Geneva - Seattle - New York
>>>> code.dblock.org - @**dblockdotorg <http://twitter.com/#!/dblockdotorg>
>>>>  - artsy.net - git**hub/dblock <https://github.com/dblock>
>>>>
>>>  --
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Heroku" group.
>>>
>>> To unsubscribe from this group, send email to
>>> heroku+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/heroku?hl=en_US?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Heroku Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to heroku+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> --
>>
>> dB. | Moscow - Geneva - Seattle - New York
>> code.dblock.org - @dblockdotorg <http://twitter.com/#!/dblockdotorg> -
>> artsy.net - github/dblock <https://github.com/dblock>
>>
>> --
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Heroku" group.
>>
>> To unsubscribe from this group, send email to
>> heroku+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/heroku?hl=en_US?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Heroku Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to heroku+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> --
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en_US?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Heroku Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 

dB. | Moscow - Geneva - Seattle - New York
code.dblock.org - @dblockdotorg <http://twitter.com/#!/dblockdotorg> -
artsy.net - github/dblock <https://github.com/dblock>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to