Hi Kawamura-san, I'm one of the PAUSE admins.
I just wanted to check that you're aware that there are quite a few other CPAN distributions dependent on Devel::CallChecker. Currently there are 13 distributions which directly use it, but including indirect dependents, there are 81 distributions reliant on Devel-CallChecker. This means that if you break Devel-CallChecker you could break up to 81 other distributions. As a result, you need to be careful when doing releases: consider doing developer releases if there are significant changes, check your CPAN Testers results after a release, and when you create a new version for release, check that it doesn't break those 13 distributions. Your request was reassuring, in the things you mentioned in your maintenance plan, but given you don't currently maintain any CPAN distributions relied on by others, I'd like to factor "CPAN River position" into you plan. Thanks, Neil On 17 Aug 2026 at 03:59 +0100, ぱんなこ <[email protected]>, wrote: > Hello PAUSE admins, > > I'd like to adopt the Devel-CallChecker distribution. > > The distribution is currently marked ADOPTME, and it still has active > downstream users. I would like to take over its maintenance and keep it > compatible with current and future Perl releases. > > My initial maintenance plan is to: > > - preserve the existing API and behavior > - establish a canonical public source repository > - add CI coverage for current Perl versions > - verify the existing XS test suite against recent Perl releases > - update distribution metadata and bug tracker information > - make conservative maintenance releases as needed > > My PAUSE ID is SHINGO. > > I have also recently started contributing maintenance fixes and tests to > other CPAN distributions as part of an effort to help maintain the Perl > ecosystem. > > Please let me know if you need any additional information. > > Best regards, > Shingo Kawamura > PAUSE ID: SHINGO
