WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #4575, comment 73


Ignore:
Timestamp:
01/09/2019 07:32:45 PM (3 years ago)
Author:
stevenkword
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4575, comment 73

    initial v1  
    88> I'm also being fairly conservative in what I move to the 5.2 milestone, as opposed to `Future Release`: only tickets that I think can realistically be reviewed and merged in 5.2 are there. So, barring unforeseen circumstances, I think it's reasonable that this enhancement can be committed in WordPress 5.2.
    99
    10 Thank you for the prompt response @pento.  That seems reasonable and I do understand the hesitation to muck with WP_Query.  I'll ensure this ticket stays in a committable state through the 5.2 cycle.  Can we please just keep an eye on it when the time comes? There are more tickets that I'd also like to shepherd through the process, but this ticket illustrates some of the challenges the contributors to this component have been facing.  I don't want Feeds to be a 2nd-class citizen.  I feel the component used a lot more than people realize and I would like to see the project address some long-standing issues in 2019.
     10Thank you for the prompt response @pento.  That seems reasonable and I do understand the hesitation to muck with WP_Query.  I'll ensure this ticket stays in a committable state through the 5.2 cycle.  Can we please just keep an eye on it when the time comes? There are more tickets that I'd also like to shepherd through the process, but this ticket illustrates some of the challenges the contributors to this component have been facing.  I don't want Feeds to be a 2nd-class citizen.  I feel the component is used a lot more than people realize and I would like to see the project address some long-standing issues in 2019.