Dual-lived modules, bug tracker

Dear porters,

what's the policy for dual-lived modules that are maintained primarily 
as part of core perl (i.e. Porting/Maintainers gives "UPSTREAM" = 
"blead") with respect to bug tracking? In principle, the bugs should be 
reported to rt.perl.org, but that doesn't stop users from reporting to 
the rt.cpan.org queue.

Supposing I can't fix all of the bugs (or rather few). Should I post a 
notice to the list?

Should I refile the bugs and close the rt.cpan.org tickets?

Cheers,
Steffen

• Dual-lived modules, bug tracker by Steffen Mueller
• Re: Dual-lived modules, bug tracker by Nicholas Clark
• Re: Dual-lived modules, bug tracker by David Golden
• Re: Dual-lived modules, bug tracker by Steffen Mueller
• Re: Dual-lived modules, bug tracker by Ruslan Zakirov
• Re: Dual-lived modules, bug tracker by Steffen Mueller
• Re: Dual-lived modules, bug tracker by Ruslan Zakirov
• Re: Dual-lived modules, bug tracker by Nicholas Clark
• Re: Dual-lived modules, bug tracker by Ruslan Zakirov
• Re: Dual-lived modules, bug tracker by Aristotle Pagaltzis
• Re: Dual-lived modules, bug tracker by Ruslan Zakirov
• Re: Dual-lived modules, bug tracker by David Golden
• Re: Dual-lived modules, bug tracker by Jesse Vincent
• Re: Dual-lived modules, bug tracker by Ruslan Zakirov
• Re: Dual-lived modules, bug tracker by David Golden
• Re: Dual-lived modules, bug tracker by Ruslan Zakirov
• Re: Dual-lived modules, bug tracker by Robert Spier