[wp-hackers] The problem with Contributions and This Thread
zamoose at gmail.com
Thu Dec 30 22:49:37 UTC 2010
Then perhaps the core team ought to either 1) expand or 2) not worry so much about each changeset and allow others to regression test.
On Dec 30, 2010, at 4:43 PM, Peter Westwood <peter.westwood at ftwr.co.uk> wrote:
> On 30 Dec 2010, at 20:44, Doug Stewart wrote:
>> On Thu, Dec 30, 2010 at 5:52 AM, Peter Westwood
>> <peter.westwood at ftwr.co.uk> wrote:
>>> Giving someone commit access to focus on lower priority tickets benefits no-one.
>>> It just causes code churn, lack of project focus, and makes it more likely that important bugs will get ignored.
>> With all due respect, where's your proof for this? I suppose that a
>> good bit of this judgement would need to be made on a ticket-by-ticket
>> basis, but still...
>> If the tickets are legitimate yet somehow lower priority, how could
>> there possibly be no benefit?
> The core team try and review every change that is made to the code to ensure that it is correct, doesn't introduce bugs etc.
> There time should be focussed on the most important bugs.
> Giving someone access to rush through all those easy trivial lower priority tickets with patches and commit them increases the workload for the core team and anyone else who reviews all the changesets.
> Therefore less time is available for important bugs.
> Peter Westwood
> http://blog.ftwr.co.uk | http://westi.wordpress.com
> C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers