develooper Front page | perl.perl5.porters | Postings from July 2009

Re: Dual-lived modules, bug tracker

Thread Previous | Thread Next
From:
Nicholas Clark
Date:
July 29, 2009 02:28
Subject:
Re: Dual-lived modules, bug tracker
Message ID:
20090729092837.GF60303@plum.flirble.org
On Wed, Jul 29, 2009 at 11:21:53AM +0200, Steffen Mueller wrote:
> 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?

Personally, I guess I'd like:

1: All the bugs fixed :-)
2: Failing that, the existing bug contents to be migrated to new bugs on
   rt.perl.org. I don't know if this is automatable for RT currently (or in
   the near future)
3: The (effectively) duplicate queues on rt.cpan.org to be closed to new
   bugs, and some way given to redirect people to report bugs via perlbug.
   Certainly close the queues to new bugs as soon as possible.

but that's just a personal opinion, and I don't have time to make any of this
happen.

Nicholas Clark

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About