Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[META] Needs expert assessment for 5.12.0 #9955

Closed
p5pRT opened this issue Nov 10, 2009 · 8 comments
Closed

[META] Needs expert assessment for 5.12.0 #9955

p5pRT opened this issue Nov 10, 2009 · 8 comments

Comments

@p5pRT
Copy link

p5pRT commented Nov 10, 2009

Migrated from rt.perl.org#70369 (status was 'resolved')

Searchable as RT70369$

@p5pRT
Copy link
Author

p5pRT commented Nov 10, 2009

From @pjf

This meta-ticket exists to track tickets that have been assessed by a
triage volunteer as being a potential candidate for inclusion the 5.12
release of Perl, but which requires an expert assessment.

@p5pRT
Copy link
Author

p5pRT commented Nov 10, 2009

@pjf - Status changed from 'new' to 'open'

@p5pRT
Copy link
Author

p5pRT commented Jul 6, 2012

From @doy

Is this ticket still useful?

-doy

@p5pRT
Copy link
Author

p5pRT commented Jul 10, 2012

From @nwc10

On Fri, Jul 06, 2012 at 09​:34​:49AM -0700, Jesse Luehrs via RT wrote​:

Is this ticket still useful?

Not with that subject :-)

But what we are missing is any sort of structure whereby anyone competent
can triage tickets, and mark those that are "seemingly valid, but I know
I don't know enough about this area to be sure".

I think that that was the intent of this ticket, and that intent is still
useful.

However, it will expose a second problem, which is that for significant
chunks of the core, *no-one* is immediately competent to assess the relevant
detail of the ticket. This holds for both bug reports, and patches. For
the latter, often it takes the "expert" a similar amount of time to validate
and understand the problem as the original patch author took on it. I'm not
sure how to solve that. The codebase is both very big and very tightly
coupled, which means that the whole doesn't fit inside anyone's head.
And most people working on it are not doing it anything like full time,
which means that their heads have to contain a bunch of other stuff.
20 people doing 2 hours a week (if *only* we had 20 people. Dream on) is
as similar to 1 person for 40 hours as the mythical 9 women making a baby
in one month.

(Just) money isn't solving this.

Nicholas Clark

@p5pRT
Copy link
Author

p5pRT commented Jan 21, 2013

From @rjbs

On Tue Jul 10 04​:16​:26 2012, nicholas wrote​:

On Fri, Jul 06, 2012 at 09​:34​:49AM -0700, Jesse Luehrs via RT wrote​:

Is this ticket still useful?

Not with that subject :-)

I don't think this ticket is useful at all. If its subject was "tickets needing assessment by expert
in {regex,optrees,XS}" or something, maybe. It's too much "hard tickets," now that it does not
relate to any specific (like blocking v5.12.0)

Has anyone found this ticket of use in the past three years?

I am closing this ticket for now. If it should be re-opened, convince me.

@p5pRT
Copy link
Author

p5pRT commented Jan 21, 2013

From @rjbs

Resolved as per threat.

--
rjbs

@p5pRT
Copy link
Author

p5pRT commented Jan 21, 2013

From [Unknown Contact. See original ticket]

Resolved as per threat.

--
rjbs

@p5pRT
Copy link
Author

p5pRT commented Jan 21, 2013

@rjbs - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant