The 'easy' tag

[Martin Pool]

2009/7/4 Jonathan Lange <jml at mumak.net>:
> I really like the idea of the 'easy' tag & am glad that we've got some
> bugs filed that way.
>
> However, a few of the bugs marked 'easy' don't have any clear notes on
> how to fix them, or why they are easy. When you mark a bug as easy,
> could you please add notes along those lines? That way it's easier to
> do opportunistic Bazaar hacking.

That's a good idea - I think the combination of these two is more
useful than the somewhat incomplete "mentor" feature.  Anyone can be
mentored on any bug.  Giving a specific clue where to start is I
suspect more helpful.

I'm thinking about doing a project, perhaps when the 2.0-targeted bugs
are done, to close allegedly easy bugs, perhaps seeing how many we can
collectively close in a 24-hour period.  Something like the Hug Day or
100 Papercuts projects that have been run in Ubuntu.  I'd like this
partly because it's annoying to have so many allegedly easy bugs open
for so long, and also just for the sake of seeing what happens.

Possible outcomes:

 * well, they were actually easy, but they also weren't really that important
 * getting easy bugs through review, pqm, etc is inefficient -- so we
could change something by eg doing branches that fix many bugs, or
doing on-call review for that day
 * many of these bugs are easy to fix but hard to test -- so we could
grant them an exemption from testing and see how that works out

-- 
Martin <http://launchpad.net/~mbp/>