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

[Michael Hendricks]

On Fri, May 11, 2012 at 11:15 AM, Florent Becker <
florent.becker at ens-lyon.org> wrote:

> Given that most bugtracker activity is mirrored on the mailing list,
> isn't the bugtracker already just a bunch of memoized, precooked
> requests into the ml archive?


Good point.  I think that part of the issue tracker is good.  A simple web
interface for reporting a bug to the mailing list could be particularly
useful for Owen's use case: capturing "what was the user trying to do?"

My concern is the different half-life of an issue in the tracker vs an
email in the list.  The former only decays with active involvement (closing
the issue).  The latter decays automatically if nobody finds it important
enough to follow up.  For a small project like darcs, rapid decay seems
like a valuable prioritization technique.

-- 
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/darcs-devel/attachments/20120514/005ea789/attachment.html>