Bug #84286 for Class-Method-Modifiers: Metadata and repository chain are a mess

Fri Mar 29 10:26:36 2013 ribasushi [...] leporine.io - Ticket created

Subject:

Metadata and repository chain are a mess

This is the first bug, for the rest I have patches, but until this is sorted I don't know what to base these patches on. Current CPAN version: 2.03 Current resposiory as per 2.03 meta: https://github.com/karenetheridge/Class-Method-Modifiers.git Latest version commit in above github repository: 2.01 Forked-from repository: https://github.com/sartak/Class-Method-Modifiers Latest version commit in above githuib repository: 2.02 Bugtracker as per 2.03 meta: https://rt.cpan.org/Public/Dist/Display.html?Name=Class-Method-Modifiers Issues present in alternative bugtracker: https://github.com/sartak/Class-Method-Modifiers/issues?state=open

Fri Mar 29 21:13:59 2013 ether [...] cpan.org - Correspondence added

Apologies -- I did the last few releases, so the github repo in the metadata is correct, but I didn't push after release. I'm too used to dzil doing this for me, but sartak doesn't want me to dzilify this dist :) I've pushed now, so what's in my repo should be the latest and match what's on cpan.

Fri Mar 29 21:14:00 2013 The RT System itself - Status changed from 'new' to 'open'

Fri Mar 29 21:14:00 2013 ether [...] cpan.org - Status changed from 'open' to 'resolved'

Fri Mar 29 21:58:38 2013 ribasushi [...] leporine.io - Correspondence added

Subject:	Re: [rt.cpan.org #84286] Metadata and repository chain are a mess
Date:	Sat, 30 Mar 2013 12:58:20 +1100
To:	Karen Etheridge via RT <bug-Class-Method-Modifiers [...] rt.cpan.org>
From:	Peter Rabbitson <ribasushi [...] cpan.org>

On Fri, Mar 29, 2013 at 09:14:00PM -0400, Karen Etheridge via RT wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=84286 > > > Apologies -- I did the last few releases, so the github repo in the metadata is correct, but I didn't push after release. I'm too used to dzil doing this for me, but sartak doesn't want me to dzilify this dist :) > > I've pushed now, so what's in my repo should be the latest and match what's on cpan.

What about the RT/Github issues thing? This I suppose is something for sartak to decide. Also wouldn't it be saner instead of doing this "repository hopping" to have the thing in gitmo (not so hot if you want to keep the github issues).

Fri Mar 29 21:58:39 2013 The RT System itself - Status changed from 'resolved' to 'open'

Fri Mar 29 22:16:05 2013 ether [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #84286] Metadata and repository chain are a mess
Date:	Fri, 29 Mar 2013 19:15:38 -0700
To:	Peter Rabbitson via RT <bug-Class-Method-Modifiers [...] rt.cpan.org>
From:	Karen Etheridge <ether [...] cpan.org>

On Fri, Mar 29, 2013 at 09:58:39PM -0400, Peter Rabbitson via RT wrote: Show quoted text

> What about the RT/Github issues thing? This I suppose is something for > sartak to decide.

The bugtracker is not set in META.yml, so the default is RT. The fact that someone created an issue against sartak's github repo anyway cannot be helped :) Show quoted text

> Also wouldn't it be saner instead of doing this "repository hopping" to > have the thing in gitmo (not so hot if you want to keep the github > issues).

Yes, it could potentially be moved to p5sagits to live with other dists in the same family (Role-Tiny, Moo etc). I can do this migration if sartak is in favour.

Fri Mar 29 22:16:34 2013 ether [...] cpan.org - Correspondence added

Come find me and/or sartak on irc to discuss more; replying to this email will re-open the issue - thanks!

Fri Mar 29 22:16:35 2013 ether [...] cpan.org - Status changed from 'open' to 'resolved'

Sat Mar 30 00:01:51 2013 ribasushi [...] leporine.io - Correspondence added

Subject:	Re: [rt.cpan.org #84286] Metadata and repository chain are a mess
Date:	Sat, 30 Mar 2013 15:01:35 +1100
To:	Karen Etheridge via RT <bug-Class-Method-Modifiers [...] rt.cpan.org>
From:	Peter Rabbitson <ribasushi [...] cpan.org>

On Fri, Mar 29, 2013 at 10:16:34PM -0400, Karen Etheridge via RT wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=84286 > > > Come find me and/or sartak on irc to discuss more; replying to this email will re-open the issue - thanks!

I am aware it does reopen the issue - the issue isn't entirely resolved :) Also you know I am not big on IRC lately - even if I drop you a line I will not be around to see the answer.

Sat Mar 30 00:01:53 2013 The RT System itself - Status changed from 'resolved' to 'open'

Sat Mar 30 00:04:00 2013 ribasushi [...] leporine.io - Correspondence added

Subject:	Re: [rt.cpan.org #84286] Metadata and repository chain are a mess
Date:	Sat, 30 Mar 2013 15:03:49 +1100
To:	Karen Etheridge via RT <bug-Class-Method-Modifiers [...] rt.cpan.org>
From:	Peter Rabbitson <ribasushi [...] cpan.org>

On Fri, Mar 29, 2013 at 10:16:06PM -0400, Karen Etheridge via RT wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=84286 > > > On Fri, Mar 29, 2013 at 09:58:39PM -0400, Peter Rabbitson via RT wrote:

> > What about the RT/Github issues thing? This I suppose is something for > > sartak to decide.

> > The bugtracker is not set in META.yml, so the default is RT. The fact that > someone created an issue against sartak's github repo anyway cannot be > helped :)

Of course it can be. There are 3 courses of actions: *) Set meta to point to RT, disable the github issues feature (there's a checkbox for that) *) Set meta to point to github issues, as such virtually "disabling" RT *) Set meta to the preferred tracker and continue accepting issues on both Cheers

Tue Apr 09 19:06:15 2013 ether [...] cpan.org - Correspondence added

There's nothing to do here -- in the absence of any metadata, the default bugtracker is RT, which sartak seems happy with (and lets all maintainers see issue reports, therefore preferred to using github issues). We can move the repo to p5sagits if we want, but that's orthogonal.

Tue Apr 09 19:06:16 2013 ether [...] cpan.org - Status changed from 'open' to 'resolved'