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 perl 5.26.0 #15222
Comments
From @khwilliamsonThis meta-ticket will be used to collect tickets blocking the release of perl 5.26.0. |
From @demerphq[perl #126182] should be considered blocking, or perhaps better put, Yves On 10 March 2016 at 18:01, Karl Williamson <perlbug-followup@perl.org> wrote:
-- |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonOn 03/10/2016 11:05 AM, yves orton via RT wrote:
#126182 already is on the list of 5.24 release blockers. No action need
|
From @demerphqOn 10 March 2016 at 19:29, Karl Williamson <khw@cpan.org> wrote:
Oh whoops. Sorry about that, i guess i got confused which release we Yves |
From @jkeenanOn Thu, 10 Mar 2016 17:01:54 GMT, khw wrote:
I'm attaching a CSV file in which I try to characterize the status of the tickets which have been classified as blockers for 5.26.0. Notes on the entries in the "status" column: "No fix by freeze; remove as blocker": "Need decision": "Needs more examination": "Need action by CPAN maintainer": "Owner's call": The "recommendation" column is just my own judgment calls. Others may have different opinions. Thank you very much. -- |
From @jkeenanOn Sat, 18 Mar 2017 00:29:05 GMT, jkeenan wrote:
Attaching. -- |
From @jkeenanperl-5.26.0 has been released. All tickets upon which this ticket depended have been resolved. Marking this ticket resolved. Thank you very much. |
@jkeenan - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#127688 (status was 'resolved')
Searchable as RT127688$
The text was updated successfully, but these errors were encountered: