[wp-hackers] Moving tickets/patches forward

[Ryan Boren]

On 10/17/07, Callum Macdonald <lists.automattic.com at callum-macdonald.com> wrote:
> I think this raises an interesting point. Is there actually a process
> for making contributions or decisions in WordPress? Or is it just what
> the core devs do, when they do it?
>
> I realise there's a great deal of discussion on the list, and that's
> great. I know that I've personally noticed westi replying to lots of
> stuff and accepting patches. Is that it, is that the process?
>
> http://codex.wordpress.org/Core_Patch_Submission
> This page is currently blank. It would be nice if there was something
> here explaining how patches should be submitted.

http://codex.wordpress.org/Submitting_Bugs covers some of this.  Not
sure what's with the Core Patch Submission page.

Patch commits tend to happen in cycles.  Right now we've been getting
2.3.1 ready and doing some architectural stuff to 2.4.  Small bugs
milestoned for 2.4 are kinda on the back burner.  In the case of
#5169, it's a bug in the somewhat orphaned and neglected wp-mail and
involves email related regular expressions, which are a pain. For an
example of what a pain it is to handle all cases for an email address:

http://trac.wordpress.org/attachment/ticket/4616/4616b.diff

Such bugs tend to get shuffled to the back of development priorities.
But, the thing to do if you care about a bug that isn't getting
traction is just what's been done here.  Add a note to trac and bring
it up on this list to see if anyone wants to take up the cause.

Anyhow, I added some notes to the ticket.

Ryan