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] tickets blocking the release of 5.25.1 #15234

Closed
p5pRT opened this issue Mar 17, 2016 · 7 comments
Closed

[META] tickets blocking the release of 5.25.1 #15234

p5pRT opened this issue Mar 17, 2016 · 7 comments
Labels

Comments

@p5pRT
Copy link

@p5pRT p5pRT commented Mar 17, 2016

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

Searchable as RT127731$

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Mar 17, 2016

From @rjbs

This is for tickets to be dealt with early in perl 5.25.x, generally meaning
deprecations that should be executed or pending branches that should be merged.

--
rjbs

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jan 6, 2017

From @jkeenan

On Thu, 17 Mar 2016 23​:52​:06 GMT, rjbs wrote​:

This is for tickets to be dealt with early in perl 5.25.x, generally
meaning
deprecations that should be executed or pending branches that should
be merged.

We're most of the way thru the 5.25.* release cycle. Can we close this META ticket?

--
James E Keenan (jkeenan@​cpan.org)

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jan 6, 2017

From [Unknown Contact. See original ticket]

On Thu, 17 Mar 2016 23​:52​:06 GMT, rjbs wrote​:

This is for tickets to be dealt with early in perl 5.25.x, generally
meaning
deprecations that should be executed or pending branches that should
be merged.

We're most of the way thru the 5.25.* release cycle. Can we close this META ticket?

--
James E Keenan (jkeenan@​cpan.org)

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jan 7, 2017

From @iabyn

On Fri, Jan 06, 2017 at 01​:03​:21PM -0800, James E Keenan via RT wrote​:

We're most of the way thru the 5.25.* release cycle. Can we close this
META ticket?

The only ticket attached to it which is still open is

  #57512​: Implicit close()s are silently unchecked for error

which AFAICT is done apart from a possible debate about whether the
new warnings should be fatalisable, which shouldn't really be a blocker
for anything.

So I'm +1 for just closing the meta ticket.

--
A walk of a thousand miles begins with a single step...
then continues for another 1,999,999 or so.

@p5pRT p5pRT closed this Jan 7, 2017
@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jan 7, 2017

@jkeenan - Status changed from 'new' to 'resolved'

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jan 7, 2017

From @xsawyerx

On 01/07/2017 04​:27 PM, Dave Mitchell wrote​:

On Fri, Jan 06, 2017 at 01​:03​:21PM -0800, James E Keenan via RT wrote​:

We're most of the way thru the 5.25.* release cycle. Can we close this
META ticket?
The only ticket attached to it which is still open is

\#57512​: Implicit close\(\)s are silently unchecked for error

which AFAICT is done apart from a possible debate about whether the
new warnings should be fatalisable, which shouldn't really be a blocker
for anything.

So I'm +1 for just closing the meta ticket.

I don't think there's any value in keeping this META ticket still open,
since the version has passed.

We can move this ticket to the 5.26.0 blocking.

(So yeah, +1)

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jan 7, 2017

From @khwilliamson

On 01/07/2017 08​:27 AM, Dave Mitchell wrote​:

On Fri, Jan 06, 2017 at 01​:03​:21PM -0800, James E Keenan via RT wrote​:

We're most of the way thru the 5.25.* release cycle. Can we close this
META ticket?

The only ticket attached to it which is still open is

\#57512​: Implicit close\(\)s are silently unchecked for error

which AFAICT is done apart from a possible debate about whether the
new warnings should be fatalisable, which shouldn't really be a blocker
for anything.

So I'm +1 for just closing the meta ticket.

In the meantime, I moved that to block 5.26.0. But I agree it shouldn't
be a blocker.

@p5pRT p5pRT added the Severity Low label Oct 19, 2019
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