Looking at the github conversation, you seem to have covered all the bases.
Probably not completely relevant, but I'm deprecating a couple of
functions in one of my modules, and I went through the slightly tedious
process of putting the deprecation announcement in BIG LETTERS in the
README file. Then a couple of versions later, I put carp() messages in the
deprecated functions themselves. Sometime in 2014, I will finally remove
the functions, over a year after the first announcement.
This may be a bit much for the Elastic[Ss]earch person though, especially
if the changes are more than simple deprecations. And I will bet you a
quarter that I will get an e-mail complaining about the missing functions
in my module anyway.
-john
On Mon, September 30, 2013 6:49 pm, Karen Etheridge wrote:
>
> The problem: ElasticSearch.pm is a module that has existed for some time
> on
> the CPAN. Elasticsearch.pm has just been uploaded quite recently,
> presenting a new API, but its installation will overwrite any existing
> ElasticSearch.pm on case-insensitive file systems.
>
> https://metacpan.org/module/ElasticSearch#DEPRECATION
>
> comments requested, on how to resolve this issue:
> https://github.com/elasticsearch/elasticsearch-perl/issues/5
>
>
