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-ticket for perl5.10.1 #9744

Closed
p5pRT opened this issue May 28, 2009 · 10 comments
Closed

Meta-ticket for perl5.10.1 #9744

p5pRT opened this issue May 28, 2009 · 10 comments

Comments

@p5pRT
Copy link

@p5pRT p5pRT commented May 28, 2009

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

Searchable as RT66092$

@p5pRT
Copy link
Author

@p5pRT p5pRT commented May 28, 2009

From @Tux

This is a place-holder/parent for bugs that stall the release of perl-5.10.1

@p5pRT
Copy link
Author

@p5pRT p5pRT commented May 28, 2009

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

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Mar 14, 2010

From @iabyn

Since 5.10.1 has been released, I guess marking this is stalled makes
sense (it shouldn't be resolved, since there are unresolved dependents)

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Mar 14, 2010

@iabyn - Status changed from 'open' to 'stalled'

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jul 6, 2012

From @doy

I think unlinking the dependents and closing it is fine.

-doy

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jul 6, 2012

From [Unknown Contact. See original ticket]

I think unlinking the dependents and closing it is fine.

-doy

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jul 6, 2012

@doy - Status changed from 'stalled' to 'resolved'

@p5pRT p5pRT closed this Jul 6, 2012
@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jul 7, 2012

From @nwc10

On Fri, Jul 06, 2012 at 04​:24​:31PM -0700, Jesse Luehrs via RT wrote​:

I think unlinking the dependents and closing it is fine.

But are all the dependents actually resolved?

(In that, if we thought that something was worth fixing for 5.10.1, but
ultimately didn't, don't we still think that it's worth fixing?)

Nicholas Clark

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jul 7, 2012

From @doy

On Sat, Jul 07, 2012 at 10​:54​:16AM +0100, Nicholas Clark wrote​:

On Fri, Jul 06, 2012 at 04​:24​:31PM -0700, Jesse Luehrs via RT wrote​:

I think unlinking the dependents and closing it is fine.

But are all the dependents actually resolved?

(In that, if we thought that something was worth fixing for 5.10.1, but
ultimately didn't, don't we still think that it's worth fixing?)

Well, yeah, that's why they are still open. If we still think we want
them to be fixed specifically by 5.18, we can add them to the 5.18 meta
ticket.

-doy

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jul 24, 2012

From @nwc10

On Sat, Jul 07, 2012 at 08​:19​:06AM -0500, Jesse Luehrs wrote​:

On Sat, Jul 07, 2012 at 10​:54​:16AM +0100, Nicholas Clark wrote​:

On Fri, Jul 06, 2012 at 04​:24​:31PM -0700, Jesse Luehrs via RT wrote​:

I think unlinking the dependents and closing it is fine.

But are all the dependents actually resolved?

(In that, if we thought that something was worth fixing for 5.10.1, but
ultimately didn't, don't we still think that it's worth fixing?)

Well, yeah, that's why they are still open. If we still think we want
them to be fixed specifically by 5.18, we can add them to the 5.18 meta
ticket.

That seems like an excellent plan. Does that ticket exist yet?
(I couldn't find it, but I can find the equivalents for 5.14.0 and 5.16.0)

This is also "interesting" in that it still has open children​:

https://rt-archive.perl.org/perl5/Ticket/Display.html?id=70369
  [META] Needs expert assessment for 5.12.0

but possibly after 2 years it deserves the same fate as

https://rt-archive.perl.org/perl5/Ticket/Display.html?id=70421
  [META] Non-critical bugs for Perl 5.12.0

in that those bugs aren't really special, if no-one has fixed them and
no-one else has reported them.

Nicholas Clark

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

Successfully merging a pull request may close this issue.

None yet
1 participant