-
Notifications
You must be signed in to change notification settings - Fork 570
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
Comments
From @TuxThis is a place-holder/parent for bugs that stall the release of perl-5.10.1 |
@Tux - Status changed from 'new' to 'open' |
From @iabynSince 5.10.1 has been released, I guess marking this is stalled makes |
@iabyn - Status changed from 'open' to 'stalled' |
From @doyI think unlinking the dependents and closing it is fine. -doy |
From [Unknown Contact. See original ticket]I think unlinking the dependents and closing it is fine. -doy |
@doy - Status changed from 'stalled' to 'resolved' |
From @nwc10On Fri, Jul 06, 2012 at 04:24:31PM -0700, Jesse Luehrs via RT wrote:
But are all the dependents actually resolved? (In that, if we thought that something was worth fixing for 5.10.1, but Nicholas Clark |
From @doyOn Sat, Jul 07, 2012 at 10:54:16AM +0100, Nicholas Clark wrote:
Well, yeah, that's why they are still open. If we still think we want -doy |
From @nwc10On Sat, Jul 07, 2012 at 08:19:06AM -0500, Jesse Luehrs wrote:
That seems like an excellent plan. Does that ticket exist yet? This is also "interesting" in that it still has open children: https://rt-archive.perl.org/perl5/Ticket/Display.html?id=70369 but possibly after 2 years it deserves the same fate as https://rt-archive.perl.org/perl5/Ticket/Display.html?id=70421 in that those bugs aren't really special, if no-one has fixed them and Nicholas Clark |
Migrated from rt.perl.org#66092 (status was 'resolved')
Searchable as RT66092$
The text was updated successfully, but these errors were encountered: