Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andreas Ericsson <ae@xxxxxx> writes:

> On 03/02/2012 08:03 AM, Junio C Hamano wrote:
>
> ... a very concise and exact response.
>
>> In any case, any solution that demands more things to be done by people
>> near the core developers than they currently are already doing will make
>> things worse by exacerbating the problem that comes from a bottleneck in
>> the process.  I do not think your "The maintainer triages and assigns
>> issues to other developers" or "The assigned developer marks the issue as
>> 'done' after fixing it" will fly very well, regardless of the use of any
>> bug tracker.
>
> It works very well when there's the incentive of roof over one's head
> and food on one's table to take care of the assigned issues.

Your "this is a volunteer effort and assignment does not work like corp
environment" is valid, but I think it is missing the point.  A solution
that demands more from people who are already bottlenecks will not work
very well, even in a corporate environment where you have stronger
incentive to fill your assigned role.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]