[darcs-devel] how can Darcs dev be more agile ?

[Florent Becker]

Le 11/05/2012 17:39, Michael Hendricks a écrit :
> Good questions Florent.  A few answered below.
> 
> On Fri, May 11, 2012 at 12:59 AM, Florent Becker <
> florent.becker at ens-lyon.org> wrote:
> 
>>> eliminate the issue tracker
>>
>> Why would you want to do that? I'm not sure I follow you. Can you explain
>> how it's an obstacle?
>>
> 
> Our issue tracker, as with most open source projects, seems to be a black
> hole for bug reports.  Reports go in and nothing useful comes out.  A
> mailing list can be a black hole too but doesn't require someone to close
> issues, manage statuses, etc.
> 
> If a bug reporter can't/won't fix the bug himself, I think it should be an
> email to the list.  If he can, it should be a patch.  Searching a list
> archive works about as well as searching an issue tracker.
> 
> Here are two articles outlining some benefits of not having an issue
> tracker:
> 
>    - http://web.archive.org/web/20080812083551/http://navarra.ca/?p=68
>    - http://www.oreillynet.com/onlamp/blog/2005/10/ofun.html
> 
I just read the second article, so I see a little better where you're
coming from. My response to this article in defence of our current way
of working is that in exchange for a heavier commit process, we have a
(relatively) light release process. I think that if we made commiting
review-free, we'd just be shifting the burden to release time when no
one is motivated to bear it.

Florent