[wp-hackers] Moving tickets/patches forward
wp-hackers at nj-arp.org
Sat Oct 20 20:32:11 GMT 2007
#5169 is all done and ready to be committed. Can it go into 2.3.1?
----- Original Message -----
From: "Ryan Boren" <ryan at boren.nu>
To: <wp-hackers at lists.automattic.com>
Sent: Thursday, October 18, 2007 1:36 AM
Subject: Re: [wp-hackers] Moving tickets/patches forward
> On 10/17/07, Callum Macdonald <lists.automattic.com at callum-macdonald.com>
>> 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?
>> 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:
> 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.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers