Track tasks and feature requests
Join 40 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprises[META] 5.23.1: patches to be considered #14593
Comments
This comment has been minimized.
This comment has been minimized.
From @jkeenanThis ticket will be used *strictly* to hold "Depends on" links to RTs *with patches attached* which are to be evaluated for application to blead *after* perl-5.22.0 is released, i.e., for perl-5.23.1. No discussion of the patches themselves in this ticket, please! Thank you very much. -- |
This comment has been minimized.
This comment has been minimized.
From @jkeenanOn Mon Mar 16 18:53:01 2015, jkeenan wrote:
With 5.22.0 having been released today, let's start working through the individual tickets listed on this META ticket. I propose to close this ticket when 5.23.1 is released. Thank you very much. -- |
This comment has been minimized.
This comment has been minimized.
From [Unknown Contact. See original ticket]On Mon Mar 16 18:53:01 2015, jkeenan wrote:
With 5.22.0 having been released today, let's start working through the individual tickets listed on this META ticket. I propose to close this ticket when 5.23.1 is released. Thank you very much. -- |
This comment has been minimized.
This comment has been minimized.
From @jkeenanThe purpose of this META ticket was to keep a list of those patches submitted before the release of 5.22.0 which could not be considered until after that release. Many of the tickets on which this ticket depended have been resolved; many have not. I have moved the latter to "Refers to" status in this ticket and removed them from "Depends on". This permits this ticket to be resolved. The "Refers to" tickets now need to be considered on their individual merits. Thank you very much. -- |
This comment has been minimized.
This comment has been minimized.
|
@jkeenan - Status changed from 'new' to 'resolved' |
Migrated from rt.perl.org#124092 (status was 'resolved')
Searchable as RT124092$