Is the cpan.org RT queue still a place to report bugs?
Closed this issue · 7 comments
As noted in https://rt.cpan.org/Public/Bug/Display.html?id=81619 there are two ways to report bugs for DBD::Firebird. As a perl old-fart I of course prefer RT, hence reported a bunch of bugs there. I can move them here if it helps? Cheers.
RT is still the official way , here i mirror the bugs for easy tracking and closing them from commits messages
the distributed bug tracker manager isn't invented yet so i think in the end we will go the perl way only with RT
Se we will not duplicate the work
Please post the merge requests and i will handle them and then i will do the release
On Wed, Dec 26, 2012 at 01:29:44AM -0800, Popa Marius Adrian wrote:
Please post the merge requests and i will handle them and then i will do the release
Sorry, EMISCOMMUNICATION ;) Are you asking me to convert the trees to
github pull requests, or git requests or...? Each RT on cpan has a link
to the tree/branch with the proposed fixes, hence my confusion.
I will do the the proposed fixes , only it was easier if you did the pull
request for each one ,
Don't worry i will solve them
On Wed, Dec 26, 2012 at 12:58 PM, Peter Rabbitson
notifications@github.comwrote:
On Wed, Dec 26, 2012 at 01:29:44AM -0800, Popa Marius Adrian wrote:
Please post the merge requests and i will handle them and then i will do
the releaseSorry, EMISCOMMUNICATION ;) Are you asking me to convert the trees to
github pull requests, or git requests or...? Each RT on cpan has a link
to the tree/branch with the proposed fixes, hence my confusion.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-11684587.
On Thu, Dec 27, 2012 at 12:27:34AM -0800, Popa Marius Adrian wrote:
I will do the the proposed fixes , only it was easier if you did the pull
request for each one ,
No problem it doesn't take that long. I just wasn't sure which way you
want to go. Will go with pull requests in the future.
I have added to the project you can merge the changes directly in the master
Hi!
Earlier you said the distributed bug tracker manager isn't invented yet so i think in the end we will go the perl way only with RT, which means you probably should disable issues on this repo (there is a button to disable issues/wikis, while pull-requests will still flow in normally). This way there is no duplicated work as you pointed out.
Cheers!