Specifying different bug trackers?
Hi, I was wondering if it were possible to point at a different bug tracker than rt.cpan.org. I know I can specify bugtracker: in META.yml, but was wondering what that actually did. Can I prevent people from opening tickets on rt.cpan,org. Does the bugtracker item in META.yml cascade through to the front page of search.cpan? How can I make the RT emails for my module NOT open a ticket, but bounce with a message, or even better, forward to my lighthouse incoming email? -- Chris Thompson
Re: Specifying different bug trackers?
* On Tue, Jan 27 2009, Chris Thompson wrote: Can I prevent people from opening tickets on rt.cpan,org. Does the bugtracker item in META.yml cascade through to the front page of search.cpan? No, it doesn't. How can I make the RT emails for my module NOT open a ticket, but bounce with a message, or even better, forward to my lighthouse incoming email? I think you will have to roll your own here. I recommend a quick procmail rule that redirects incoming mail from RT to your own bug tracker. Really though, RT.CPAN is quite nice these days. You can even connect to it with SD and work on tickets offline. I find this much nicer than maintaining my own infrastructure. Regards, Jonathan Rockway -- print just = another = perl = hacker = if $,=$
Re: Specifying different bug trackers?
On Jan 27, 2009, at 2:52 PM, Jonathan Rockway wrote: Can I prevent people from opening tickets on rt.cpan,org. Does the bugtracker item in META.yml cascade through to the front page of search.cpan? No, it doesn't. Yes, it does. See http://cpansearch.perl.org/src/PETDANCE/ack-1.86/META.yml and how it reflects on http://search.cpan.org/dist/ack/ Now, it doesn't prevent tickets from opening in rt.cpan.org, and that's just one of those things you'll have to bear. I get probably 10% of my bug reports on WWW::Mechanize in RT, instead of the bug tracker at code.google.com. It would be nice if rt.cpan.org allowed authors to shut down queues, but hey, I'm not arguing with a free service. xoxo, Andy -- Andy Lester = a...@petdance.com = www.petdance.com = AIM:petdance
Re: Specifying different bug trackers?
On Tue, Jan 27, 2009 at 03:42:23PM -0600, Andy Lester wrote: It would be nice if rt.cpan.org allowed authors to shut down queues, but hey, I'm not arguing with a free service. When I requested it, a queue was shut. I believe the correct address for requests is rt-cpan-ad...@bestpractical.com Nicholas Clark
Re: Specifying different bug trackers?
* On Tue, Jan 27 2009, Andy Lester wrote: On Jan 27, 2009, at 2:52 PM, Jonathan Rockway wrote: Can I prevent people from opening tickets on rt.cpan,org. Does the bugtracker item in META.yml cascade through to the front page of search.cpan? No, it doesn't. Yes, it does. See http://cpansearch.perl.org/src/PETDANCE/ack-1.86/META.yml and how it reflects on http://search.cpan.org/dist/ack/ Ah, I read this as the front page of RT.CPAN, which is not aware of anything in META.yml. It would be nice if rt.cpan.org allowed authors to shut down queues, but hey, I'm not arguing with a free service. The idea is for something to exist for when authors Go Away, their email address stops working, and their own bugtracker 404s. Of course, RT also works when the author is still around. :) Regards, Jonathan Rockway -- print just = another = perl = hacker = if $,=$
Re: Specifying different bug trackers?
On Tue, Jan 27, 2009 at 5:27 PM, Jonathan Rockway j...@jrock.us wrote: The idea is for something to exist for when authors Go Away, their email address stops working, and their own bugtracker 404s. Of course, RT also works when the author is still around. :) On the other hand, maybe rt.cpan.org could become META.yml-aware and redirect accordingly. -- David
Re: Specifying different bug trackers?
# from David Golden
# on Tuesday 27 January 2009 14:50:
On the other hand, maybe rt.cpan.org could become META.yml-aware and
redirect accordingly.
That's a lovely idea. Ambitious implementors may want to read:
http://use.perl.org/~Eric+Wilhelm/journal/38304
--Eric
--
perl -e 'srand; print join( ,sort({rand() 0.5}
qw(sometimes it is important to be consistent)));'
---
http://scratchcomputing.com
---
