From hello at mikestemle.com Tue Jan 2 03:01:43 2024 From: hello at mikestemle.com (Mike Stemle) Date: Tue, 2 Jan 2024 06:01:43 -0500 Subject: [Philadelphia-pm] Thoughts on communicating with users Message-ID: Hey all. After 8 years of maintenance releases of this `Net::AMQP::RabbitMQ` module, I've come to the unpleasant but realistic conclusion that the Perl module?as well as the C library it binds to?are suffering from terminal code rot. The OpenSSL version is EOL'ed, and there is so much code duplication that I inherited when I started maintaining it that keeping up with the changes to the C library has become unsustainable. I've been trying to get my users to share their thoughts on paths forward, but it's kinda difficult. I could use ideas on how to better message to people that I am looking for ideas. Here's the GitHub Discussion: https://github.com/net-amqp-rabbitmq/net-amqp-rabbitmq/discussions/241 If this were Node, I'd add a deprecation notice to the install scripts and cut another maintenance release, but for the life of me I think of an idiomatically correct way to do this for CPAN installs. I could use something like a test which prints out a big ol' warning, but if someone is installing it as just another module in a larger list of modules, they won't see it. Does anybody have any suggestions for how best to do this? ~ Mike Stemle hello at mikestemle.com https://github.com/manchicken -------------- next part -------------- An HTML attachment was scrubbed... URL: